CVE-2011-0493 json
Tor before 0.2.1.29 and 0.2.2.x before 0.2.2.21-alpha might allow remote attackers to cause a denial of service (assertion failure and daem…
published 2011-01-19 15 y ago modified 2026-06-16 4 mo ago also EUVD-2011-0513
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.5%
- EPSS 2.5% chance of exploitation in 30 days, percentile 84%
- public exploits
- 0
- none known
Summary
Tor before 0.2.1.29 and 0.2.2.x before 0.2.2.21-alpha might allow remote attackers to cause a denial of service (assertion failure and daemon exit) via vectors related to malformed router caches and improper handling of integer values.
Patch / fix
- tor Debian 14, Debian 13, Debian 12 0.2.1.29-1
debian advisories DEBIAN-CVE-2011-0493
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-0493 updated cvss 7.5
tor: multiple security flaws fixed in 0.2.1.29
-
Red Hat All currently supported Red Hat productsnot 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
2.52% chance of exploitation in the next 30 days, higher than 84% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:N/A:P |
Classification
- Weakness
-
- CWE-189 Numeric Errors
References
-
archives.seul.org
/or/announce/Jan-2011/msg00000.html
mailing-list, patch
-
gitweb.torproject.org
/tor.git/blob/refs/heads/release-0.2.2:/ChangeLog
patch
-
blog.torproject.org
/blog/tor-02129-released-security-patches
patch
- trac.torproject.org /projects/tor/ticket/2352
-
exchange.xforce.ibmcloud.com
/vulnerabilities/64864
vdb-entry
-
securityfocus.com
/bid/45953
vdb-entry
Sources
- CVE List CVE-2011-0493
- NVD CVE-2011-0493
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.