Vulnerability Details : CVE-2021-28089
Tor before 0.4.5.7 allows a remote participant in the Tor directory protocol to exhaust CPU resources on a target, aka TROVE-2021-001.
Products affected by CVE-2021-28089
- cpe:2.3:o:fedoraproject:fedora:33:*:*:*:*:*:*:*
- cpe:2.3:a:torproject:tor:*:*:*:*:*:*:*:*
- cpe:2.3:a:torproject:tor:*:*:*:*:*:*:*:*
- cpe:2.3:a:torproject:tor:*:*:*:*:*:*:*:*
- cpe:2.3:a:torproject:tor:0.4.4.0:alpha:*:*:*:*:*:*
- cpe:2.3:a:torproject:tor:0.4.4.1:alpha:*:*:*:*:*:*
- cpe:2.3:a:torproject:tor:0.4.4.2:alpha:*:*:*:*:*:*
- cpe:2.3:a:torproject:tor:0.4.4.3:alpha:*:*:*:*:*:*
Exploit prediction scoring system (EPSS) score for CVE-2021-28089
0.23%
Probability of exploitation activity in the next 30 days
EPSS Score History
~ 61 %
Percentile, the proportion of vulnerabilities that are scored at or less
CVSS scores for CVE-2021-28089
Base Score | Base Severity | CVSS Vector | Exploitability Score | Impact Score | Score Source | First Seen |
---|---|---|---|---|---|---|
5.0
|
MEDIUM | AV:N/AC:L/Au:N/C:N/I:N/A:P |
10.0
|
2.9
|
NIST | |
7.5
|
HIGH | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
3.9
|
3.6
|
NIST |
CWE ids for CVE-2021-28089
-
The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources.Assigned by: nvd@nist.gov (Primary)
References for CVE-2021-28089
-
https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/HPDXB2GZHG3VNOTWSXQ3QZVHNV76WCU5/
[SECURITY] Fedora 33 Update: tor-0.4.5.7-1.fc33 - package-announce - Fedora Mailing-ListsMailing List;Third Party Advisory
-
https://security.gentoo.org/glsa/202107-25
Tor: Multiple vulnerabilities (GLSA 202107-25) — Gentoo securityThird Party Advisory
-
https://gitlab.torproject.org/tpo/core/tor/-/issues/40304
Not FoundVendor Advisory
-
https://blog.torproject.org/node/2009
New releases (with security fixes): Tor 0.3.5.14, 0.4.4.8, and 0.4.5.7 | Tor BlogRelease Notes;Vendor Advisory
Jump to