GHSA-qf3c-rw9f-jh7v — nautobot-device-onboarding
MEDIUMGHSA-qf3c-rw9f-jh7v is a medium-severity (CVSS 5.7) vulnerability in nautobot-device-onboarding. A fix is available for nautobot-device-onboarding — see the affected versions and patch details below.
Clear Text Credentials Exposed via Onboarding Task
Real-World Exposure
nautobot-device-onboardingReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
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 NAPALM_USERNAME & NAPALM_PASSWORD from nautobot_config.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
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | nautobot-device-onboarding | ≥ 2.0.0&&< 3.0.0 | 3.0.0pip install --upgrade 'nautobot-device-onboarding==3.0.0' |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for nautobot-device-onboarding, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update nautobot-device-onboarding to 3.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qf3c-rw9f-jh7v is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-qf3c-rw9f-jh7v can be triaged on real exposure rather than presence alone.
Tailored to GHSA-qf3c-rw9f-jh7v. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-qf3c-rw9f-jh7v in your dependencies?
O3 Security finds GHSA-qf3c-rw9f-jh7v across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.