CVE-2005-2050 Information disclosure in n/a
Medium 5.0
Published
Updated
Check this codebase for CVE-2005-2050 and fix it if it is affected.
What it is: CVE-2005-2050 is a medium-severity vulnerability in Tor Tor, published on 26 Jun 2005. 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-2005-2050 in the wild and no public exploit code.
Affected product: Tor Tor. 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-2005-2050/ (Markdown: https://insights.sbomify.com/CVE-2005-2050/index.md)
Remote attackers can read arbitrary memory and key information from Tor exit servers, compromising anonymity and security.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2005-2050?
CVE-2005-2050 is a medium-severity vulnerability in Tor Tor, published on 26 Jun 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
Unknown vulnerability in Tor before 0.1.0.10 allows remote attackers to read arbitrary memory and possibly key information from the exit server's process space.
Which versions are affected by CVE-2005-2050?
It affects 1 product.
Products include Tor Tor.
How do I fix CVE-2005-2050?
Upgrade to a fixed version.
Is CVE-2005-2050 being exploited?
There is no known exploitation of CVE-2005-2050 in the wild and no public exploit code.
Other vulnerabilities in Tor Tor
- CVE-2010-1676 Memory corruption in n/a
- CVE-2009-0939 Tor before 0.2.0.34 treats incomplete IPv4 addresses as valid, which has unknown impact and attack vectors related to "Spec conformance," as
- CVE-2009-0414 Memory corruption in n/a
- CVE-2008-5398 Information disclosure in n/a
- CVE-2011-2778 Memory corruption in n/a
Sources
Also known as DEBIAN-CVE-2005-2050, GHSA-pg8c-8fmq-494r.