First published: Tue Jan 14 2020(Updated: )
### Impact An attacker who can gain file access to the repository and modify metadata files may cause a denial of service to clients by creating many invalid signatures on a metadata file. Having a large number of signatures to verify will delay the moment when the client will determine the signature is not valid. This delay may be for at least a few minutes, but possibly could be longer especially if multiple files are impacted. The tuf maintainers would like to thank Erik MacLean of Analog Devices, Inc. for reporting this issue. ### Patches No fix exists for this issue. ### Workarounds No workarounds are known for this issue. ### References * [CVE-2020-6173](https://nvd.nist.gov/vuln/detail/CVE-2020-6173) * [Issue #973](https://github.com/theupdateframework/tuf/issues/973)
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Linuxfoundation The Update Framework | >=0.7.2<=0.12.1 | |
pip/tuf | >=0.7.2<0.12.2 | 0.12.2 |
>=0.7.2<=0.12.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2020-6173 is a vulnerability in TUF (The Update Framework) versions 0.7.2 through 0.12.1 that allows uncontrolled resource consumption.
CVE-2020-6173 has a severity rating of medium, with a CVSS score of 5.3.
The versions of TUF affected by CVE-2020-6173 range from 0.7.2 to 0.12.1.
To fix CVE-2020-6173, upgrade TUF to a version higher than 0.12.1.
You can find more information about CVE-2020-6173 on the official GitHub repository of TUF, including the commits and issues related to the vulnerability.