Skip to content

GHSA-q6r9-r9pw-4cf7 CVE-2025-2887

tough failure to detect delegated target rollback

Medium crates.io
Severity
0.0 / 10
Medium · CVSS 4.0
Exploit chance (EPSS)
0.33%
Chance of exploitation in the next 30 days. Higher than 26.48% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-1025 Comparison Using Wrong Factors
Fix
0.20.0
Upgrade tough to this version or later

Description

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.

Affected versions

crates.io

PackageVulnerableFixed in
tough
< 0.20.0
0.20.0

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

tough crates.io → 0.20.0

cargo
cargo update -p tough --precise 0.20.0

Severity breakdown

CVSS 4.0 0.0

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

Attack vector
Network
Attack complexity
High
Attack requirements
None
Privileges required
High
User interaction
Passive
Confidentiality (vulnerable system)
None
Integrity (vulnerable system)
High
Availability (vulnerable system)
None
Confidentiality (subsequent systems)
None
Integrity (subsequent systems)
None
Availability (subsequent systems)
None

CVSS 3.1 4.2

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

Attack vector
Network
Attack complexity
High
Privileges required
High
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Weakness

CWE-1025: Comparison Using Wrong Factors

The code performs a comparison between two entities, but the comparison examines the wrong factors or characteristics of the entities, which can lead to incorrect results and resultant weaknesses.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-4v58-8p28-2rq3
awslabs/tough is Missing Delegated Metadata Validation
Medium Also affects tough
GHSA-8m7c-8m39-rv4x
awslabs/tough Delegated Roles have a Signature Threshold Bypass
Medium Also affects tough
GHSA-j8x2-777p-23fc
tough cyclic delegation graphs are not detected
Low Also affects tough
GHSA-76g3-38jv-wxh4
tough timestamp metadata is cached when it fails snapshot rollback check
Medium Also affects tough
GHSA-v4wr-j3w6-mxqc
tough terminating targets role delegations are not respected
Medium Also affects tough
GHSA-5vmp-m5v2-hx47
tough root metadata version is not checked for sequential versioning
Medium Also affects tough
GHSA-r56q-vv3c-6g9c
Improper sanitization of delegated role names
High Also affects tough
GHSA-x3r5-q6mj-m485
Improper sanitization of target names
High Also affects tough
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor