Skip to content
Noroxi
CVE-2007-4174· NVD / CVE Program· CNA mitre

Tor before 0.1.2.16, when ControlPort is enabled, does not properly restrict commands to localhost port 9051, which allows remote attackers

Tor before 0.1.2.16, when ControlPort is enabled, does not properly restrict commands to localhost port 9051, which allows remote attackers to modify the torrc configuration file, compromise anonymity, and have other unspecified impact via HTTP POST data containing commands without valid authentication, as demonstrated by an HTML form (1) hosted on a web site or (2) injected by a Tor exit node.

MediumCVSS 5.8 · v2.0—Proof of concept Fix available
Published
Aug 7, 2007
Updated
Jun 16, 2026
EPSS
6.2% · 93th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

25

Monitor

Low priority for now.

CVSS
23 / 40 · 5.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
2 / 30 · 6.2%

Affected systems

VendorProduct
tortor

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • tor torup to 0.1.2.15 inclusive
  • tor tor0.1.2.1
  • tor tor0.1.2.10
  • tor tor0.1.2.11
  • tor tor0.1.2.12
  • tor tor0.1.2.13
  • tor tor0.1.2.14
  • tor tor0.1.2.2
  • tor tor0.1.2.3
  • tor tor0.1.2.4
  • tor tor0.1.2.5
  • tor tor0.1.2.6
  • tor tor0.1.2.7
  • tor tor0.1.2.8
  • tor tor0.1.2.9

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12torbefore 0.1.2.16-10.1.2.16-1

Same product

tor: all records

Other highest-scoring records for the same primary product.

  • CVE-2010-1676Heap-based buffer overflow in Tor before 0.2.1.28 and 0.2.2.x before 0.2.2.20-alpha allows remote attackers to cause a denial of service (da
    42Plan
  • CVE-2009-0939Tor before 0.2.0.34 treats incomplete IPv4 addresses as valid, which has unknown impact and attack vectors related to "Spec conformance," as
    41Plan
  • CVE-2009-0414Unspecified vulnerability in Tor before 0.2.0.33 has unspecified impact and remote attack vectors that trigger heap corruption.
    41Plan
  • CVE-2008-5398Tor before 0.2.0.32 does not properly process the ClientDNSRejectInternalAddresses configuration option in situations where an exit relay is
    38Monitor
  • CVE-2011-2778Multiple heap-based buffer overflows in Tor before 0.2.2.35 allow remote attackers to cause a denial of service (memory corruption) or possi
    31Monitor
  • CVE-2006-3409Integer overflow in Tor before 0.1.1.20 allows remote attackers to execute arbitrary code via crafted large inputs, which result in a buffer
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:tor0.1.2.16-1 · Debian:12Package registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Exploit-DB entry ×2

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Exploit-DB entryremote2007-08-02
Exploit-DB entryremote2007-09-29

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. First PoC-5 d
  2. Published
  3. TodaySep 30, 2026+6994 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Technical details

Attack conditions

    If successful

    Confidentiality
    P · data can be read
    Integrity
    P · data or configuration can be modified
    Availability
    none
    Attack complexity
    M
    Confidentiality impact
    P
    Integrity impact
    P
    Availability impact
    None

    CVSS vector

    AV:N/AC:M/Au:N/C:P/I:P/A:N

    nvd-primary

    Attack context

    MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

    MITRE has no CAPEC/ATT&CK mapping for this CWE.

    Noroxi analysis

    No Noroxi analysis for this record yet

    We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

    We use this product, ask for help

    Change log

    1. Fix✗ → ✓

    For records you follow, these changes also arrive as notifications. →

    References

    All records