tuf
Affected
- introduced
0.14.0, fixed0.16.0(ecosystem)
Fixed versions
0.16.0
Fix
- Fixed version
0.16.0pip install --upgrade tuf==0.16.0
Advisory
Also known as: None
Python-TUF vulnerable to incorrect threshold signature computation for new root metadata
Impact
The function _verify_root_self_signed(), introduced in v0.14.0, and which verifies self-signatures in a new root metadata file, counted multiple signatures by any new root key towards the new threshold. That is, any single new root key could theoretically provide enough signatures to meet the threshold for new key self-signatures required during root metadata update.
A scenario where this attack could be relevant is amazingly unlikely in practice to the point where labeling this issue as a security advisory is potentially overstating the impact of the issue. Given that new root keys only become trusted by the client after a successful root metadata update, which also requires the quorum of signatures from old trusted root keys, this issue has been evaluated as low in severity.
In particular, in order to exploit this vulnerability, an attacker must:
Patches
A fix is available since version 0.16.0.
Workarounds
No workarounds are known for this issue.
References
Low Basis: The source's own band: LOW
0.14.0, fixed 0.16.0 (ecosystem)0.16.0
0.16.0pip install --upgrade tuf==0.16.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