CVE-2020-6173 json
Client Denial of Service on TUF
published 6y ago modified 4mo ago also GHSA-2828-9vh6-9m6j , PYSEC-2020-146 , EUVD-2020-0225
- cvss
- 5.3
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.8%
- EPSS 1.8% chance of exploitation in 30 days, percentile 78%
- public exploits
- 0
- none known
Summary
TUF (aka The Update Framework) 0.7.2 through 0.12.1 allows Uncontrolled Resource Consumption.
Patch / fix
- pypi tuf 0.12.2
Is CVE-2020-6173 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.76% chance of exploitation in the next 30 days, higher than 78% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/theupdateframework/tuf/issues/973 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:N/A:P |
| GitHub | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | tuf | >=0.7.2, <0.12.2 >=0.7.5, <0.12.2 |
0.12.2 |
Classification
- Weakness
-
- CWE-400 Uncontrolled Resource Consumption
References
-
github.com
/theupdateframework/tuf/commits/develop
web, patch, third-party-advisory
-
github.com
/theupdateframework/tuf/issues/973
web, exploit, issue-tracking, patch, third-party-advisory, report
-
github.com
/theupdateframework/tuf/security/advisories/GHSA-2828-9vh6-9m6j
web
-
nvd.nist.gov
/vuln/detail/CVE-2020-6173
advisory
-
github.com
/pypa/advisory-database/tree/main/vulns/tuf/PYSEC-2020-146.yaml
web
-
github.com
/theupdateframework/tuf
package
-
github.com
/advisories/GHSA-2828-9vh6-9m6j
advisory
Sources
- CVE List CVE-2020-6173
- GitHub Advisory GHSA-2828-9vh6-9m6j
- NVD CVE-2020-6173
- OSV PYSEC-2020-146
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.