Nx OsOperating system · Cisco
CVE-2024-20286
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA vulnerability in the Python interpreter of Cisco NX-OS Software could allow an authenticated, low-privileged, local attacker to escape the Python sandbox and gain unauthorized access to the underlying operating system of the device. The vulnerability is due to insufficient validation of user-supplied input. An attacker could exploit this vulnerability by manipulating specific functions within the Python interpreter. A successful exploit could allow an attacker to escape the Python sandbox and execute arbitrary commands on the underlying operating system with the privileges of the authenticated user. Note: An attacker must be authenticated with Python execution privileges to exploit these vulnerabilities. For more information regarding Python execution privileges, see product-specific documentation, such as the section of the Cisco Nexus 9000 Series NX-OS Programmability Guide.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThis is a Python sandbox escape vulnerability in Cisco NX-OS Software where insufficient input validation in the Python interpreter allows an authenticated low-privileged user to escape the sandbox and execute arbitrary commands on the underlying operating system with the privileges of the authenticated user.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Nx OsOperating system
= 9.3\(13\)CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check the Cisco NX-OS software versionExecute 'show version' on the NX-OS device and locate the software version in the outputAffected if The version displayed is exactly 9.3(13)
-
Verify Python interpreter feature statusExecute 'show feature | include python' or 'show running-config | include python' to determine if the Python interpreter feature is enabledAffected if Python feature is listed as enabled or the Python sandbox configuration is present
-
Confirm user access to Python sandboxCheck which users or roles have permission to execute Python commands by reviewing 'show role' or 'show user' configurations, or attempt to access the Python interpreter via the CLIAffected if Authenticated users (including low-privileged users) have access to the Python interpreter/sandbox
-
Identify Python execution permissionsReview the NX-OS role-based access control (RBAC) configuration for Python execution permissions using 'show role feature-group' and 'show role feature'Affected if Users with 'python' or 'guest-user' roles can invoke the Python interpreter
A system is affected if it runs NX-OS version 9.3(13) and has the Python interpreter feature enabled with accessible execution permissions for authenticated users.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedApply the vendor patch/upgrade to Cisco NX-OS Software to address this vulnerability, and review Python execution permissions to ensure only necessary personnel have access.
Cisco NX-OS 9.3(14) or later in the 9.3 train, or the next stable release for your platform family
- 1. Identify the current Cisco NX-OS version running on the affected device using 'show version'
- 2. Check Cisco's official security advisory for CVE-2024-20286 on sec.cloudapps.cisco.com or www.cisco.com to identify the specific fixed release for your platform
- 3. Plan an upgrade window following change management procedures
- 4. Back up the current configuration using 'copy running-config startup-config' or 'backup' to a remote location
- 5. Download the fixed NX-OS release from Cisco (typically 9.3(14) or later for the 9.3 train, or migrate to a newer supported train)
- 6. Upgrade the NX-OS software following Cisco's standard upgrade procedures
- 7. Verify the upgrade completed successfully and the device is operational
- 8. Confirm the Python sandbox escape vulnerability is resolved by verifying the NX-OS version
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Nx Os
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-20286 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-20286 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data