Skip to content
Noroxi
NVD / CVE Program· CNA redhat

CVE-2012-4419: The compare_tor_addr_to_addr_policy function in or/policies.c in Tor before 0.2.2.39, and 0.2.3.x before 0.2.3.21-rc, allows remote…

MediumCVSS 5.0 · v2.0—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 21/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 2.1% (FIRST EPSS); higher than 82.4% of all records.
  • No special conditions are required; it is repeatable.
  • Fixed version: tor (Debian:12) 0.2.3.22-rc-1; tor (Debian:6.0) 0.2.2.39-1; tor (openSUSE:Tumbleweed) 0.2.8.11-1.1.

Low priority for now. Upgrade to tor (Debian:12) 0.2.3.22-rc-1; tor (Debian:6.0) 0.2.2.39-1; tor (openSUSE:Tumbleweed) 0.2.8.11-1.1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

The compare_tor_addr_to_addr_policy function in or/policies.c in Tor before 0.2.2.39, and 0.2.3.x before 0.2.3.21-rc, allows remote attackers to cause a denial of service (assertion failure and daemon exit) via a zero-valued port field that is not properly handled during policy comparison.

Published
Sep 14, 2012
Updated
Jun 16, 2026
EPSS
2.1% · 82th percentile
CWE
—

Report tools

JSON

Action score

21

Monitor

Low priority for now.

CVSS
20 / 40 · 5.0 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 2.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2012-4419

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for torproject records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
torprojecttor

Affected versions

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

  • torproject torup to 0.2.2.38 inclusive
  • torproject tor0.0.2
  • torproject tor0.0.3
  • torproject tor0.0.4
  • torproject tor0.0.5
  • torproject tor0.0.6
  • torproject tor0.0.6.1
  • torproject tor0.0.6.2
+12 more rows
  • torproject tor0.0.7
  • torproject tor0.0.7.1
  • torproject tor0.0.7.2
  • torproject tor0.0.7.3
  • torproject tor0.0.8.1
  • torproject tor0.0.9.1
  • torproject tor0.0.9.10
  • torproject tor0.0.9.2
  • torproject tor0.0.9.3
  • torproject tor0.0.9.4
  • torproject tor0.0.9.5
  • torproject tor0.0.9.6

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12torbefore 0.2.3.22-rc-10.2.3.22-rc-1
Debian:6.0torbefore 0.2.2.39-10.2.2.39-1
openSUSE:Tumbleweedtorbefore 0.2.8.11-1.10.2.8.11-1.1

Same product

torproject: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-77642tor before 0.4.9.9 was prone to an out-of-bounds write when parsing a consensus or detached signature with unexpected signature digest…
    37Monitor
  • CVE-2026-77638Tor before 0.4.9.11 is prone to a race condition where in just the right circumstances a rendezvous point could man-in-the-middle…
    36Monitor
  • CVE-2026-44603Tor before 0.4.9.7 has an out-of-bounds read by one byte via a malformed BEGIN cell, aka TROVE-2026-007.
    36Monitor

Published before and after this one in the same product

  • Later →CVE-2012-4922Sep 14, 2012 · The tor_timegm function in common/util.c in Tor before 0.2.2.39, and 0.2.3.x before 0.2.3.22-rc, does not properly validate time values…
    21Monitor
  • Later →CVE-2012-5573Jan 1, 2013 · The connection_edge_process_relay_cell function in or/relay.c in Tor before 0.2.3.25 maintains circuits even if an unexpected SENDME cell…
    21Monitor
  • Later →CVE-2013-7295Jan 17, 2014 · Tor before 0.2.4.20, when OpenSSL 1.x is used in conjunction with a certain HardwareAccel setting on Intel Sandy Bridge and Ivy Bridge…
    17Monitor

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.2.3.22-rc-1 · Debian:12Package registry (OSV)
opensuse:tor0.2.8.11-1.1 · openSUSE:TumbleweedPackage registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

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.

No dated events beyond publication.

Patch and commit links

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

Bug bounty scope

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

Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate.

Technical details

Attack conditions

  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
P · the service can be disrupted
Attack complexity
Low
Confidentiality impact
None
Integrity impact
None
Availability impact
P

Weakness class (CWE)

—

CVSS vector

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

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.

References

Show all references (8 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records