# CVE-2014-5117: Information disclosure in n/a

> Remote attackers can identify hidden service names by analyzing RELAY cell patterns, compromising user anonymity in Tor networks.

- **Severity:** Medium 5.8 (`AV:N/AC:M/Au:N/C:P/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:** 30 Jul 2014
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2014-5117, DSA-2993-1, GHSA-v73p-8445-35p5, MGASA-2014-0312, UBUNTU-CVE-2014-5117

## What is CVE-2014-5117?

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

### Official description

Tor before 0.2.4.23 and 0.2.5 before 0.2.5.6-alpha maintains a circuit after an inbound RELAY_EARLY cell is received by a client, which makes it easier for remote attackers to conduct traffic-confirmation attacks by using the pattern of RELAY and RELAY_EARLY cells as a means of communicating information about hidden service names.

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

It affects 1 product.


Products: Torproject Tor.

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

Upgrade to a fixed version.

## Is CVE-2014-5117 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2026-77638](https://insights.sbomify.com/CVE-2026-77638/): Race condition in Tor (high 8.9)
- [CVE-2026-77642](https://insights.sbomify.com/CVE-2026-77642/): Memory corruption in Tor (high 7.5)
- [CVE-2022-33903](https://insights.sbomify.com/CVE-2022-33903/): Denial of service in n/a (high 7.5)
- [CVE-2021-38385](https://insights.sbomify.com/CVE-2021-38385/): Denial of service in n/a (high 7.5)
- [CVE-2021-34548](https://insights.sbomify.com/CVE-2021-34548/): Security feature bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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