tuf
Affected
- introduced
0, fixed0.12.0(ecosystem)
Fixed versions
0.12.0
Fix
- Fixed version
0.12.0pip install --upgrade tuf==0.12.0
Advisory
Also known as: CVE-2020-15163, PYSEC-2020-145
Invalid root may become trusted root in The Update Framework (TUF)
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, which is included in v0.14.0 of tuf.
Patches
A fix, is available in version 0.12 and newer.
Workarounds
No workarounds are known for this issue.
References
Medium Basis: The source's own band: MODERATE
0, fixed 0.12.0 (ecosystem)0.12.0
0.12.0pip install --upgrade tuf==0.12.0Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0