Security readout for executives and security teams
Plain-English summary
If an organization ran an old Tor relay without setting a Nickname, Tor could publish the machine’s local hostname as the relay nickname. That could expose internal naming details. The sources describe information disclosure only, not system compromise or code execution.
Executive priority
Treat as low urgency unless the organization operated Tor relays in the affected configuration. The main business risk is unintended disclosure of internal naming information, not direct compromise.
Technical view
CVE-2011-4897 affects Tor before 0.2.2.25-alpha when configured as a relay without the Nickname option. In that configuration, Tor used the local hostname as Nickname, allowing remote attackers to obtain potentially sensitive information by reading that value.
Likely exposure
Exposure is limited to Tor relay deployments running versions before 0.2.2.25-alpha with no explicit Nickname configured. The provided affected-product metadata is sparse, but the CVE description specifically identifies Tor relays.
Exploitation context
The bundle does not show KEV listing or confirmed active exploitation. The issue appears passively observable: the sensitive value is the relay nickname derived from the host’s local hostname.
Researcher notes
The record lacks CVSS, CWE, and detailed affected CPE data. Analysis should stay tied to the specific described condition: old Tor relay, missing Nickname, hostname exposed as nickname.
Mitigation direction
- Upgrade affected Tor relay software to 0.2.2.25-alpha or later.
- Set an explicit non-sensitive Nickname for any Tor relay.
- Review vendor guidance before changing relay configuration.
- Avoid hostnames that disclose internal roles, locations, or ownership.
Validation and detection
- Inventory any Tor relay instances and record their Tor versions.
- Check relay configuration for an explicit Nickname option.
- Review published relay nickname values for hostname leakage.
- Confirm no relay runs a version before 0.2.2.25-alpha.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2011-4897 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://blog.torproject.org/blog/tor-02225-alpha-outCVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.