# CVE-2014-0685: Security feature bypass in n/a

> Remote attackers can bypass ACL deny statements in Cisco Nexus 1000V InterCloud by sending crafted IGMP packets, allowing unauthorized network access.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 May 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-6c8c-rmvf-4c76

## What is CVE-2014-0685?

CVE-2014-0685 is a medium-severity vulnerability in n/a, published on 7 May 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Cisco 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.

Weakness: CWE-264

## Which versions are affected by CVE-2014-0685?

It affects 1 product.


Products: Cisco Cisco Nexus 1000v Intercloud.

## How do I fix CVE-2014-0685?

No fix has been published for CVE-2014-0685 yet. Limit exposure of the affected software until one is available.

## Is CVE-2014-0685 being exploited?

There is no known exploitation of CVE-2014-0685 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2014-3367](https://insights.sbomify.com/CVE-2014-3367/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-0685 and fix it if it is affected.

What it is: CVE-2014-0685 is a medium-severity vulnerability in n/a, published on 7 May 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-0685 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2014-0685/ (Markdown: https://insights.sbomify.com/CVE-2014-0685/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2014-0685
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2014-0685
- OSV: https://osv.dev/vulnerability/CVE-2014-0685

---
From sbomify Insights: https://insights.sbomify.com/CVE-2014-0685/
Summaries are generated and may contain mistakes; the official description above is the record.