CVE-2011-4897
Tor before 0.2.2.25-alpha, when configured as a relay without the Nickname configuration option,...
Tor before 0.2.2.25-alpha, when configured as a relay without the Nickname configuration option, uses the local hostname as the Nickname value, which allows remote attackers to obtain potentially sensitive information by reading this value.
Exploit likelihood
What each source reports
NVD Score used
4.3
Tor before 0.2.2.25-alpha, when configured as a relay without the Nickname configuration option, uses the local hostname as the Nickname value, which allows remote attackers to obtain potentially sensitive information by reading this value.
- Record
CVE-2011-4897- CVSS 2.0
- 4.3 Medium
AV:N/AC:M/Au:N/C:P/I:N/A:N - Weakness
- CWE-200
- Updated
- 2026-11-02
CVE List No score
Tor before 0.2.2.25-alpha, when configured as a relay without the Nickname configuration option, uses the local hostname as the Nickname value, which allows remote attackers to obtain potentially sensitive information by reading this value.
- Record
CVE-2011-4897- Updated
- 2026-11-02
EUVDEUVD-2011-4814 No score
Tor before 0.2.2.25-alpha, when configured as a relay without the Nickname configuration option, uses the local hostname as the Nickname value, which allows remote attackers to obtain potentially sensitive information by reading this value.
- Record
EUVD-2011-4814- Updated
- 2026-11-03
GitHub AdvisoriesGHSA-7h3x-gchg-chhg No score
Tor before 0.2.2.25-alpha, when configured as a relay without the Nickname configuration option,...
Tor before 0.2.2.25-alpha, when configured as a relay without the Nickname configuration option, uses the local hostname as the Nickname value, which allows remote attackers to obtain potentially sensitive information by reading this value.
- Record
GHSA-7h3x-gchg-chhg- Weakness
- CWE-200
- Updated
- 2026-11-02
OSV No score
Tor before 0.2.2.25-alpha, when configured as a relay without the Nickname configuration option, uses the local hostname as the Nickname value, which allows remote attackers to obtain potentially sensitive information by reading this value.
- Record
CVE-2011-4897- Updated
- 2026-11-02
OSVDEBIAN-CVE-2011-4897 No score
Tor before 0.2.2.25-alpha, when configured as a relay without the Nickname configuration option, uses the local hostname as the Nickname value, which allows remote attackers to obtain potentially sensitive information by reading this value.
- Record
DEBIAN-CVE-2011-4897- Updated
- 2026-11-02
OSVopenSUSE-SU-2024:10423-1 No score
tor-0.2.8.11-1.1 on GA media
These are all security issues fixed in the tor-0.2.8.11-1.1 package on the GA media of openSUSE Tumbleweed.
- Record
openSUSE-SU-2024:10423-1- Updated
- 2026-11-02
Affected products
Affected packages
History
| Recorded | Changed | Sources |
|---|---|---|
| aliases | EUVD | |
| first indexed | CVE List, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2011-4897 is a medium vulnerability (CVSS 4.3) in Tor, published December 23, 2011. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 1.53%, the 74th percentile. Fixed in tor 0.2.2.27-beta-1.
References
blog.torproject.org/blog/tor-02225-alpha-out
nvd.nist.gov/vuln/detail/CVE-2011-4897
github.com/advisories/GHSA-7h3x-gchg-chhg
security-tracker.debian.org/tracker/CVE-2011-4897
suse.com/security/cve/CVE-2011-0427
suse.com/security/cve/CVE-2011-2768
Show 20 moreShow less
suse.com/security/cve/CVE-2011-2769
suse.com/security/cve/CVE-2011-2778
suse.com/security/cve/CVE-2011-4576
suse.com/security/cve/CVE-2011-4894
suse.com/security/cve/CVE-2011-4895
suse.com/security/cve/CVE-2011-4896
suse.com/security/cve/CVE-2011-4897
suse.com/security/cve/CVE-2012-3517
suse.com/security/cve/CVE-2012-3518
suse.com/security/cve/CVE-2012-3519
suse.com/security/cve/CVE-2012-4419
suse.com/security/cve/CVE-2012-4922
suse.com/security/cve/CVE-2012-5573
suse.com/security/cve/CVE-2013-7295
suse.com/security/cve/CVE-2014-0160
suse.com/security/cve/CVE-2014-5117
suse.com/security/cve/CVE-2015-2688
suse.com/security/cve/CVE-2015-2689
suse.com/security/cve/CVE-2015-2928
suse.com/security/cve/CVE-2015-2929