Quick answers
- Is CVE-2020-6173 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2020-6173 being exploited in the wild.
- How severe is CVE-2020-6173?
- Low severity, with a CVSS score of 3.1, published 14 January 2020.
- Which products and versions are affected?
- tuf (PyPI) ECOSYSTEM:introduced=0.7.2,fixed=0.12.2, ECOSYSTEM:introduced=0.7.5,fixed=0.12.2.
- Is there a fix for CVE-2020-6173?
- Yes. tuf (PyPI): upgrade to 0.12.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2020-6173 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2020-6173?
- Check whether you run tuf (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- tuf (PyPI): upgrade to 0.12.2 or later
pip install "tuf>=0.12.2"
Technical details
This vulnerability is a denial of service issue in the TUF client signature verification process (CWE-400: Uncontrolled Resource Consumption). An attacker who gains write access to the repository metadata can create metadata files with a large number of invalid signatures. The vulnerable TUF client will attempt to verify each signature sequentially, delaying the moment when it determines that all signatures are invalid. This delay can extend to minutes or longer, particularly when multiple metadata files are affected. The attack requires repository file access; no network exploitation or user interaction is needed. No patch has been released for this issue.
Affected products
- The Update Framework TUF 0.7.2 through 0.12.1
Identifiers
- CVE-2020-6173
- GHSA-2828-9vh6-9m6j
- PYSEC-2020-146
Timeline
- 2020-08-21: disclosed