Advisory

GHSA-f8mr-jv2c-v8mg

Also known as: CVE-2020-15163, PYSEC-2020-145

Summary

Invalid root may become trusted root in The Update Framework (TUF)

Details

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

  • Pull request resolving the invalid root becoming trusted issue PR 885
  • Pull request implementing self verification of newly downloaded root metadata PR 1101

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2020-09-09 17:29 UTC
Modified
2026-09-10 03:48 UTC

Affected packages and fixes

tuf

PyPI · All systems

Affected

  • introduced 0, fixed 0.12.0 (ecosystem)

Fixed versions

0.12.0

Fix

  • Fixed version 0.12.0
    pip install --upgrade tuf==0.12.0

Fix 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

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences