Skip to content
Fencer Intel
medium 4.3

CVE-2011-4896 json

Tor before 0.2.2.24-alpha continues to use a reachable bridge that was previously configured but is not currently configured, which might a…

published 2011-12-23 14 y ago modified 2026-06-16 4 mo ago also EUVD-2011-4813

cvss
4.3
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.5%
EPSS 1.5% chance of exploitation in 30 days, percentile 74%
public exploits
0
none known

Summary

Tor before 0.2.2.24-alpha continues to use a reachable bridge that was previously configured but is not currently configured, which might allow remote attackers to obtain sensitive information about clients in opportunistic circumstances by monitoring network traffic to the bridge port.

Patch / fix

  • tor Debian 14, Debian 13, Debian 12 0.2.2.27-beta-1

debian advisories DEBIAN-CVE-2011-4896

  • tor openSUSE Tumbleweed 0.2.8.11-1.1

opensuse advisories openSUSE-SU-2024:10423-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2011-4896 updated cvss 5.0

Tor Bridge information disclosure

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.50% chance of exploitation in the next 30 days, higher than 74% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:P/I:N/A:N

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.