CVE-2020-15163: Invalid root may become trusted root in The Update Framework (TUF)
First published: Wed Sep 09 2020(Updated: )
### Impact The Python TUF reference implementation `tuf<0.12` will incorrectly trust a previously downloaded root metadata file which failed verification at download time. This allows an attacker who is able to serve multiple new versions of root metadata (i.e. by a man-in-the-middle attack) culminating in a version which has not been correctly signed to control the trust chain for future updates. While investigating the reported vulnerability, we discovered that the detailed client workflow was not fully implemented. Specifically, for step 1.3 the newly downloaded root metadata was not being verified with a threshold of keys specified in the new root metadata file. This missing step of the client workflow has been implemented in [PR #1101](https://github.com/theupdateframework/tuf/pull/1101), which is included in [v0.14.0](https://github.com/theupdateframework/tuf/releases/tag/v0.14.0) of tuf. ### Patches A [fix](https://github.com/theupdateframework/tuf/pull/885), is available in version [0.12](https://github.com/theupdateframework/tuf/releases/tag/v0.12.0) and newer. ### Workarounds No workarounds are known for this issue. ### References * Pull request resolving the invalid root becoming trusted issue [PR 885](https://github.com/theupdateframework/tuf/pull/885) * Pull request implementing self verification of newly downloaded root metadata [PR 1101](https://github.com/theupdateframework/tuf/pull/1101)
Credit: security-advisories@github.com security-advisories@github.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Linuxfoundation The Update Framework | <0.12.0 | |
| pip/tuf | >=0<0.12.0 | 0.12.0 |
| <0.12.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://github.com/theupdateframework/tuf/commit/3d342e648fbacdf43a13d7ba8886aaaf07334af7
- https://github.com/theupdateframework/tuf/pull/885
- https://github.com/theupdateframework/tuf/releases/tag/v0.12.0
- https://github.com/theupdateframework/tuf/security/advisories/GHSA-f8mr-jv2c-v8mg
- https://pypi.org/project/tuf
- https://nvd.nist.gov/vuln/detail/CVE-2020-15163
- https://github.com/pypa/advisory-database/tree/main/vulns/tuf/PYSEC-2020-145.yaml
- https://github.com/advisories/GHSA-f8mr-jv2c-v8mg (Advisory)
Frequently Asked Questions
What is the vulnerability ID for this issue?
The vulnerability ID is CVE-2020-15163.
What is the severity of CVE-2020-15163?
The severity of CVE-2020-15163 is high with a CVSS score of 8.2.
What is Python TUF?
Python TUF (The Update Framework) is a secure software updater framework for Python.
What version of Python TUF is affected by CVE-2020-15163?
Python TUF reference implementation before version 0.12.0 is affected by CVE-2020-15163.
How can I fix CVE-2020-15163?
To fix CVE-2020-15163, update to Python TUF version 0.12.0 or later.
- collector/nvd-index
- agent/weakness
- agent/type
- collector/mitre-cve
- source/MITRE
- agent/title
- agent/remedy
- agent/severity
- collector/github-advisory-latest
- source/GitHub
- alias/GHSA-f8mr-jv2c-v8mg
- alias/CVE-2020-15163
- agent/software-canonical-lookup
- agent/last-modified-date
- agent/references
- agent/description
- agent/first-publish-date
- agent/author
- agent/softwarecombine
- agent/event
- collector/nvd-cve
- source/NVD
- collector/github-advisory
- agent/tags
- agent/trending
- vendor/linuxfoundation
- canonical/linuxfoundation the update framework
- package-manager/pip