LiveActive security incident?Get immediate response
CVE Record

CVE-2007-1103: Tor does not verify a node's uptime and bandwidth advertisements, which allows remote attackers who operate...

Tor does not verify a node's uptime and bandwidth advertisements, which allows remote attackers who operate a low resource node to make false claims of greater resources, which places the node into use for many circuits and compromises the anonymity of traffic sources and destinations.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's Takeunknown

Analyst readout for executives and security teams

Plain-English summary

This CVE describes an anonymity risk in Tor: a weak relay could falsely advertise high uptime and bandwidth, causing it to be selected for more circuits. If successful, this could expose relationships between traffic sources and destinations. The bundle does not identify affected versions or a confirmed fix.

Executive priority

Treat this as a legacy anonymity assurance issue, not a confirmed current emergency. Prioritize if the organization relied on old Tor versions for sensitive communications or still runs unvalidated Tor components.

Technical view

Tor reportedly did not verify relay self-advertised uptime and bandwidth. A low-resource malicious node could inflate those attributes, increase circuit selection probability, and improve chances of observing traffic positions relevant to anonymity compromise. The record provides no CVSS, CWE, product/version mapping, or patch details.

Likely exposure

Exposure applies to Tor deployments or users affected by the 2007 relay-selection behavior. The source bundle lists affected vendor, product, and versions as n/a, so current exposure cannot be determined from these sources alone.

Exploitation context

CISA KEV is false, and the bundle does not cite observed active exploitation. The described attacker must operate a malicious Tor node and benefit from false resource advertisements being trusted by the network.

Researcher notes

The evidence is sparse: no affected versions, CVSS vector, CWE, or remediation reference are present. Analysis should stay tied to the 2007 low-resource routing attack discussion and avoid assuming modern Tor remains affected.

Mitigation direction

  • Check Tor Project advisories and release notes for the relevant fixed behavior.
  • Upgrade Tor components to supported versions approved by the vendor.
  • Retire or isolate legacy Tor deployments that cannot be version-validated.
  • For anonymity-critical use, reassess trust in historical Tor threat assumptions.

Validation and detection

  • Inventory Tor clients, relays, and embedded Tor dependencies.
  • Map each deployment to exact Tor versions and release dates.
  • Review vendor notes for bandwidth and uptime verification changes.
  • Confirm unsupported or unknown-version deployments are removed or upgraded.
Prepared
Confidence
medium
Sources
5

Based on public source material and reviewed before publication.

Potential ATT&CK relevance

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 · low confidence lookup

CVE-2007-1103 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
0Timeline events
0ADP providers
6Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.