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.
History

Fri, 28 Mar 2025 15:15:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Thu, 27 Mar 2025 22:45:00 +0000

Type Values Removed Values Added
Description 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.
Title Improper timestamp caching during snapshot rollback in tough
Weaknesses CWE-1025
References
Metrics cvssV4_0

{'score': 5.7, 'vector': 'CVSS:4.0/AV:N/AC:H/AT:N/PR:H/UI:P/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N'}


cve-icon MITRE

Status: PUBLISHED

Assigner: AMZN

Published:

Updated: 2025-03-28T14:33:40.221Z

Reserved: 2025-03-27T21:08:16.138Z

Link: CVE-2025-2888

cve-icon Vulnrichment

Updated: 2025-03-28T14:33:21.587Z

cve-icon NVD

Status : Awaiting Analysis

Published: 2025-03-27T23:15:35.717

Modified: 2025-03-28T18:11:40.180

Link: CVE-2025-2888

cve-icon Redhat

No data.