Advisory Database
  • Advisories
  • Dependency Scanning
  1. cargo
  2. ›
  3. tough
  4. ›
  5. CVE-2025-2888

CVE-2025-2888: tough timestamp metadata is cached when it fails snapshot rollback check

March 28, 2025 (updated April 2, 2025)

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.

References

  • aws.amazon.com/security/security-bulletins/AWS-2025-007
  • github.com/advisories/GHSA-76g3-38jv-wxh4
  • github.com/awslabs/tough
  • github.com/awslabs/tough/commit/9b400e1c8b7d6b9ab8009104fa7fe5884db05f18
  • github.com/awslabs/tough/security/advisories/GHSA-76g3-38jv-wxh4
  • nvd.nist.gov/vuln/detail/CVE-2025-2888

Code Behaviors & Features

Detect and mitigate CVE-2025-2888 with GitLab Dependency Scanning

Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →

Affected versions

All versions before 0.20.0

Fixed versions

  • 0.20.0

Solution

Upgrade to version 0.20.0 or above.

Impact 4.2 MEDIUM

CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:N/I:N/A:H

Learn more about CVSS

Weakness

  • CWE-1025: Comparison Using Wrong Factors

Source file

cargo/tough/CVE-2025-2888.yml

Spotted a mistake? Edit the file on GitLab.

  • Site Repo
  • About GitLab
  • Terms
  • Privacy Statement
  • Contact

Page generated Tue, 13 May 2025 00:15:56 +0000.