# CVE-2007-4174: Missing authorization in n/a

> Remote attackers can modify Tor configuration and compromise anonymity via unauthenticated HTTP POST requests when ControlPort is enabled.

- **Severity:** Medium 5.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 7 Aug 2007
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2007-4174, GHSA-qprc-v4xr-fwgr

## What is CVE-2007-4174?

CVE-2007-4174 is a medium-severity missing authorization vulnerability in Tor Tor, published on 7 Aug 2007. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-264

## Which versions are affected by CVE-2007-4174?

It affects 1 product.


Products: Tor Tor.

## How do I fix CVE-2007-4174?

Upgrade to a fixed version.

## Is CVE-2007-4174 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-4174 exists.

Public exploit code:

- Tor 0.1.2.15 - ControlPort Missing Authentication Unauthorized Access (exploitdb)
- Tor < 0.1.2.16 - ControlPort Remote Rewrite (exploitdb)

## Other vulnerabilities in Tor Tor

- [CVE-2010-1676](https://insights.sbomify.com/CVE-2010-1676/): Memory corruption in n/a (critical 10.0)
- [CVE-2009-0939](https://insights.sbomify.com/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 (critical 10.0)
- [CVE-2009-0414](https://insights.sbomify.com/CVE-2009-0414/): Memory corruption in n/a (critical 10.0)
- [CVE-2008-5398](https://insights.sbomify.com/CVE-2008-5398/): Information disclosure in n/a (critical 9.3)
- [CVE-2011-2778](https://insights.sbomify.com/CVE-2011-2778/): Memory corruption in n/a (high 7.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-4174 and fix it if it is affected.

What it is: CVE-2007-4174 is a medium-severity missing authorization vulnerability in Tor Tor, published on 7 Aug 2007. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-4174 exists.

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-2007-4174/ (Markdown: https://insights.sbomify.com/CVE-2007-4174/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2007-4174
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2007-4174
- OSV: https://osv.dev/vulnerability/CVE-2007-4174

---
From sbomify Insights: https://insights.sbomify.com/CVE-2007-4174/
Summaries are generated and may contain mistakes; the official description above is the record.
