CVE-2025-2887: Failure to detect delegated target rollback in tough
Summary
When updating the snapshot role, TUF clients should ensure that any previously encountered targets or delegated targets metadata files continue to be present in new snapshot metadata files. Likewise, the new targets and delegated targets metadata versions must be greater than or equal to the previously encountered versions. While tough will perform this check for targets metadata files, it did not perform this check for delegated targets files.
Impact
tough could fail to detect cases where delegated targets metadata was removed or rolled back to a previous version. As a result, tough could trust and download outdated targets that it should reject.
Impacted versions: < v0.20.0
Patches
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.
Workarounds
There is no recommended work around. Customers are advised to upgrade to version 0.20.0 or the latest version.
References
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
Acknowledgement
These issues were identified by the TUF-Conformance project. We would like to thank Google for collaborating on this issue through the coordinated vulnerability disclosure process.
Other sources
During a target rollback, the client fails to detect the rollback for delegated targets. This could cause the client to fetch a target from an incorrect source, altering the target contents. Users should upgrade to tough version 0.20.0 or later and ensure any forked or derivative code is patched to incorporate the new fixes.
— NVD
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-2887?
CVE-2025-2887 has been classified with a severity that can potentially allow clients to fetch targets from incorrect sources.
How do I fix CVE-2025-2887?
To fix CVE-2025-2887, upgrade to tough version 0.20.0 or later.
Which software is affected by CVE-2025-2887?
CVE-2025-2887 affects tough versions below 0.20.0.
What is the impact of CVE-2025-2887 on my system?
CVE-2025-2887 may lead to unauthorized target content modification due to rollback detection failure.
Is there a patch available for CVE-2025-2887?
Yes, upgrading to tough version 0.20.0 or later effectively addresses the vulnerability.