Python TUF (The Update Framework) reference implementation before version 0.12 it 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 person-in-the-middle attack) culminating in a version which has not been correctly signed to control the trust chain for future updates. This is fixed in version 0.12 and newer.
The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.
| Link | Tags |
|---|---|
| https://github.com/theupdateframework/tuf/security/advisories/GHSA-f8mr-jv2c-v8mg | third party advisory |
| https://github.com/theupdateframework/tuf/pull/885 | third party advisory patch |
| https://github.com/theupdateframework/tuf/releases/tag/v0.12.0 | third party advisory |
| https://pypi.org/project/tuf | product vendor advisory |
| https://github.com/theupdateframework/tuf/commit/3d342e648fbacdf43a13d7ba8886aaaf07334af7 | broken link |