dbcve.org
Nx OsOperating system · Cisco

CVE-2014-3330

MEDIUM · 5.0 CVSS v2.0 Published 2014-08-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
Cisco NX-OS 6.1(2)I2(1) on Nexus 9000 switches does not properly process packet-drop policy checks for logged packets, which allows remote attackers to bypass intended access restrictions via a flood of packets matching a policy that contains the log keyword, aka Bug ID CSCuo02489.

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 · moderate confidence

Cisco NX-OS 6.1(2)I2(1) on Nexus 9000 switches fails to properly process packet-drop policy checks when packets match an ACL or policy containing the 'log' keyword. An attacker can flood packets matching such a logged policy to bypass intended access restrictions and have those packets processed despite matching drop rules.

MitigationUpgrade NX-OS to a version beyond 6.1(2)I2(1) that addresses CSCuo02489, or avoid using the 'log' keyword in ACLs/policies on affected versions until patching is feasible.

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
Affected:= 6.1\(2\)i2\(1\)
Nexus 9000Hardware / appliance
Affected:all versions

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
Network
Complexity
Low
Authentication
None
Confidentiality
Partial
Integrity
None
Availability
None

AV:N/AC:L/Au:N/C:P/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check NX-OS version on the Nexus 9000 switch
    Execute 'show version' or 'show install all status' from the command line interface and locate the 'NXOS' or 'system' version line
    Affected if The installed NX-OS version is 6.1(2)I2(1) or if running any version of NX-OS on a Nexus 9000 switch (per the 'all versions' advisory scope)
  2. Identify ACLs or policies containing the 'log' keyword
    Run 'show running | include log' or use 'show ip access-lists' and 'show mac access-lists' to list all access control lists, then search each ACL configuration for the 'log' keyword
    Affected if Any ACL, policy map, or traffic filter is configured with the 'log' keyword (this is the condition required for the flaw to trigger)
  3. Verify if logged ACLs include drop or deny statements
    For each ACL found with 'log', inspect its entries using 'show ip access-list <acl-name>' and check whether there are 'deny' or 'drop' rules present in the same list
    Affected if An ACL containing the 'log' keyword also has deny/drop rules that should block traffic but may be bypassed per this vulnerability
  4. Check for traffic matching logged deny policies
    If possible, review packet capture data, NetFlow records, or 'show access-lists' hit counts to observe whether traffic is being processed through a deny rule that also contains 'log'
    Affected if Packets are being processed (allowed) despite matching a deny entry that includes the 'log' keyword, indicating potential exploitation

You are affected if running NX-OS 6.1(2)I2(1) or any NX-OS version on a Nexus 9000 switch and you have ACLs or policies with the 'log' keyword that contain deny/drop rules, as the vulnerability allows traffic to bypass drop rules when 'log' is present.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade NX-OS to a version beyond 6.1(2)I2(1) that addresses CSCuo02489, or avoid using the 'log' keyword in ACLs/policies on affected versions until patching is feasible.

Fix this in Nx Os Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-3330 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-3330 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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