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

> Man-in-the-middle attackers can downgrade security protocols in ZeroMQ C++ library via crafted connection requests.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Oct 2014
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2014-7202, GHSA-4jwc-wmvr-fwp2, UBUNTU-CVE-2014-7202

## What is CVE-2014-7202?

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

### Official description

stream_engine.cpp in libzmq (aka ZeroMQ/C++)) 4.0.5 before 4.0.5 allows man-in-the-middle attackers to conduct downgrade attacks via a crafted connection request.

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

It affects 1 product.


Products: Zeromq Zeromq.

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

Upgrade to a fixed version.

## Is CVE-2014-7202 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-9721](https://insights.sbomify.com/CVE-2014-9721/): Security feature bypass in n/a (medium 4.3)
- [CVE-2014-7203](https://insights.sbomify.com/CVE-2014-7203/): Other in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-7202 is a medium-severity vulnerability in n/a, published on 8 Oct 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-7202 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-7202/ (Markdown: https://insights.sbomify.com/CVE-2014-7202/index.md)
```

## Sources

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

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