CVE-2014-0685
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 Nexus 1000V InterCloud 5.2(1)IC1(1.2) and earlier for VMware allows remote attackers to bypass ACL deny statements via crafted (1) IGMPv2 or (2) IGMPv3 packets, aka Bug ID CSCug61691.
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 confidenceCisco Nexus 1000V InterCloud versions 5.2(1)IC1(1.2) and earlier for VMware contains a flaw where crafted IGMPv2 or IGMPv3 packets can bypass configured ACL deny statements, allowing traffic to reach protected network segments despite ACL enforcement.
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<= 5.2\(1\)ic1\(1.2\)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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Cisco Nexus 1000V InterCloud is deployedIdentify whether your virtual infrastructure includes Cisco Nexus 1000V InterCloud for VMware. Check your vCenter inventory or consult your virtualization administration team for installed VEM (Virtual Ethernet Module) modules identifying as InterCloud.Affected if The product is not present in the environment, so the vulnerability does not apply.
-
Determine the installed InterCloud versionRun 'show version' on the Nexus 1000V InterCloud VSM (Virtual Supervisor Module) or query the VEM via 'show module' to obtain the exact software version. Compare the version string against 5.2(1)IC1(1.2) or earlier.Affected if The installed version is 5.2(1)IC1(1.2) or any earlier version within the 5.2(1)IC1 train.
-
Verify ACLs are configured for IGMP trafficRun 'show ip access-lists' and review any ACLs applied to interfaces or VLANs. Identify if any permit or deny statements explicitly reference IGMP (protocol 2) or any ACLs applied to segments where IGMP traffic is expected.Affected if ACLs with IGMP-related rules are configured, as the flaw allows crafted IGMP packets to bypass these deny statements.
-
Inspect IGMP configuration and trafficRun 'show ip igmp interface' to view IGMP-enabled interfaces, and use packet capture or 'show ip traffic' to observe incoming IGMPv2 or IGMPv3 packets on affected segments.Affected if IGMP is enabled and traffic is being processed, making the ACL bypass relevant.
You are affected if Cisco Nexus 1000V InterCloud version 5.2(1)IC1(1.2) or earlier is running with ACLs configured to filter IGMP traffic.
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 dataApply the Cisco software update addressing Bug ID CSCUG61691, or implement supplementary network-level filtering to block malformed IGMP packets at perimeter devices.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-0685 — 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-0685 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