Delegations are a mechanism defined by the TUF specification that allow multiple different identities to provide and sign content within a single repository. Terminating delegations and delegation priority give a TUF repository unambiguous control over how overlapping delegations are resolved. tough erroneously will not terminate a search as required, and will accept information from a lower-priority delegation that should have been ignored.
When interacting with TUF repositories that use delegations, the tough client could fetch targets owned by the incorrect role. An actor which had delegated ownership of a subset of a TUF repository could provide arbitrary contents to tough clients for targets owned by the delegating identity.
Impacted versions: < v0.20.0
A fix for this issue is available in tough version 0.20.0 and later. Customers are advised to upgrade to version 0.20.0 or later and ensure any forked or derivative code is patched to incorporate the new fixes.
There is no recommended work around. Customers are advised to upgrade to version 0.20.0 or the latest version.
If you have any questions or comments about this advisory we ask that you contact AWS/Amazon Security via our vulnerability reporting page [1] or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue.
[1] Vulnerability reporting page: https://aws.amazon.com/security/vulnerability-reporting
We would like to thank Google for collaborating on this issue through the coordinated vulnerability disclosure process.
{ "nvd_published_at": "2025-03-27T23:15:35Z", "cwe_ids": [ "CWE-670" ], "severity": "MODERATE", "github_reviewed": true, "github_reviewed_at": "2025-03-28T22:13:00Z" }