Clear Text Credentials Exposed via Onboarding Task

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.7 · CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N

EPSS

• CVE-2023-48700: 0.41% estimated exploitation activity in the next 30 days; percentile 35.73 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact When credentials are provided while creating an OnboardingTask they may be visible via the Job Results view under the Additional Data tab as args for the Celery Task execution. This only applies to OnboardingTasks that are created with credentials specified while on v2.0.0-2.0.2 of Nautobot Device Onboarding. This advisory does not apply earlier version or when using NAPALMUSERNAME & NAPALMPASSWORD from nautobotconfig.py Patches v3.0.0 Workarounds None Recommendations Delete all Job Results for any onboarding task to remove clear text credentials from database entries that were run while on v2.0.X Upgrade to v3.0.0 Rotate any exposed credential

Published by the source

21 Nov 2023, 23:50 UTC

Last modified by the source

10 Sep 2026, 03:49 UTC

Source last checked

26 Oct 2026, 13:27 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-qf3c-rw9f-jh7v

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-qf3c-rw9f-jh7v

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-48700

Advisory: Clear Text Credentials Exposed via Onboarding Task
IDs: CVE-2023-48700, GHSA-qf3c-rw9f-jh7v
Record: https://patchnext.com/advisories/cve-2023-48700 (revision 2, source checked 26 Oct 2026, 13:27 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: nautobot-device-onboarding 3.0.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI nautobot-device-onboarding: affected >= 2.0.0, < 3.0.0; fixed in 3.0.0

## Suggested inspection (read-only)
- `python -m pip show nautobot-device-onboarding`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on nautobot-device-onboarding.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-qf3c-rw9f-jh7v (OSV record GHSA-qf3c-rw9f-jh7v lists affected ranges: PyPI nautobot-device-onboarding >=2.0.0 <3.0.0 (fixed))
- Verified: https://github.com/advisories/GHSA-qf3c-rw9f-jh7v (GitHub-reviewed advisory GHSA-qf3c-rw9f-jh7v lists affected ranges: PyPI nautobot-device-onboarding >=2.0.0 <3.0.0)

Commands are suggestions: review each one before running it.