CVE-2025-2888: Improper timestamp caching during snapshot rollback in tough
Summary
TUF repositories use the timestamp role to protect against rollback events by enabling an automated process to periodically sign the role's metadata. While tough will ensure that the version of snapshot metadata in new timestamp metadata files was always greater than or equal to the previously trusted version, it will only do so after persisting the timestamp metadata to its cache.
Impact
If the tough client successfully detects a rollback event in which timestamp metadata contains outdated snapshot metadata, the invalid timestamp metadata will still be persisted to cache as trusted. tough may then subsequently incorrectly identify valid timestamp metadata as being rolled back, preventing the client from consuming valid updates.
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 snapshot rollback, the client incorrectly caches the timestamp metadata. If the client checks the cache when attempting to perform the next update, the update timestamp validation will fail, preventing the next update until the cache is cleared. 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-2888?
CVE-2025-2888 is considered a significant vulnerability due to its impact on update processes.
How do I fix CVE-2025-2888?
To fix CVE-2025-2888, you should upgrade to the latest version of the Tough software beyond version 0.20.0.
What are the potential risks of CVE-2025-2888?
The main risk of CVE-2025-2888 is that clients may fail to validate updates properly, potentially leading to outdated or incorrect data being used.
Who is affected by CVE-2025-2888?
Users of the Tough software version 0.20.0 and earlier are affected by CVE-2025-2888.
What happens if I don’t address CVE-2025-2888?
If CVE-2025-2888 is not addressed, users may not be able to perform updates successfully, resulting in stalled operations and possible data integrity issues.