Nx OsOperating system · Cisco
CVE-2014-0676
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 · uneditedCisco NX-OS allows local users to bypass intended TACACS+ command restrictions via a series of multiple commands, aka Bug ID CSCum47367.
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 vulnerability allows local users on Cisco NX-OS devices to bypass intended TACACS+ command restrictions by executing a series of multiple commands. The authorization bypass enables users who should be restricted to certain commands to circumvent those controls through a specific command sequence.
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
all versionsCVSS 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
- Authentication
- Single
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/AC:L/Au:S/C:C/I:C/A:C
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.
-
Confirm the device is running Cisco NX-OSRun 'show version' and look for 'NX-OS' in the output. Note the software version listed.Affected if The device runs any version of Cisco NX-OS (all versions are affected per the CVE)
-
Verify TACACS+ is configured on the deviceRun 'show running-config | include tacacs' or 'show tacacs-server' to check for TACACS+ server configurationAffected if TACACS+ is configured and used for authentication/authorization
-
Check if TACACS+ command authorization is enabledRun 'show running-config | include aaa authorization' or 'show aaa authorization' to see if command authorization is mapped to TACACS+Affected if Command authorization is configured to use TACACS+ servers (this is the vulnerable configuration)
-
Identify the configured command restrictionsRun 'show running-config' and look for TACACS+ server-specific command sets or command groups defined in the configurationAffected if Specific commands or command groups are restricted via TACACS+ authorization
-
Review the TACACS+ server policy configurationAccess the TACACS+ server (if accessible) and review the command authorization policy files or tables to see what restrictions are definedAffected if The TACACS+ server contains command authorization policies that could be bypassed through sequential command execution
A user is affected if the NX-OS device has TACACS+ configured with command authorization restrictions, as the vulnerability allows bypassing those restrictions through specific command sequences.
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.
From vendor dataReview and strengthen TACACS+ command authorization configurations on affected NX-OS devices. Consider implementing additional command logging and monitoring to detect bypass attempts.
Fix this in Nx Os
Scoped from the published advisory
- Consultation4.0 h
- Implementation6.0 h
- Testing4.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-0676 — 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-2014-0676 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