Update denial via pre-validation timestamp caching
Published Mar 27, 2025 · Updated Oct 14, 2025
Denial of service in AWS tough before 0.20.0 allows remote authenticated users to block valid updates via stale timestamp metadata. The client persists new timestamp metadata to its cache before validating that the referenced snapshot version has not rolled back, so rejected stale metadata becomes trusted. Exploitation requires high-privilege control of repository metadata and a client update; the poisoned cache blocks later valid updates until cleared.
Summary
What happened
Denial of service in AWS tough before 0.20.0 allows remote authenticated users to block valid updates via stale timestamp metadata. The client persists new timestamp metadata to its cache before validating that the referenced snapshot version has not rolled back, so rejected stale metadata becomes trusted. Exploitation requires high-privilege control of repository metadata and a client update; the poisoned cache blocks later valid updates until cleared.
The record
- CVE
- CVE-2025-2888
- Published
- Mar 27, 2025
- Updated
- Oct 14, 2025
- Vendor
- Amazon Web Services
- Product
- tough
- Classifications
- CWE-1025, CAPEC-25, T1499.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 27, 2025CVE publishedPublication date reported by the CVE source.
- Oct 14, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.1.0 <0.20.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo