crates.io package
tough
pkg:cargo/tough
Vulnerabilities (9)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2026-6967 | Med | 5.9 | >= 0.9.0, < 0.22.0 | 0.22.0 | Apr 24, 2026 | Missing expiration, hash, and length enforcement in delegated metadata validation in awslabs/tough before tough-v0.22.0 allows remote authenticated users with delegated signing authority to bypass TUF specification integrity checks for delegated targets metadata and poison the lo | |
| CVE-2026-6966 | Med | 5.3 | < 0.22.0 | 0.22.0 | Apr 24, 2026 | Improper verification of cryptographic signature uniqueness in delegated role validation in awslabs/tough before tough-v0.22.0 allows remote authenticated users to bypass the TUF signature threshold requirement by duplicating a valid signature, causing the client to accept forged | |
| CVE-2025-2888 | — | < 0.20.0 | 0.20.0 | Mar 27, 2025 | 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 t | ||
| CVE-2025-2887 | — | < 0.20.0 | 0.20.0 | Mar 27, 2025 | During a target rollback, the client fails to detect the rollback for delegated targets. This could cause the client to fetch a target from an incorrect source, altering the target contents. Users should upgrade to tough version 0.20.0 or later and ensure any forked or derivative | ||
| CVE-2025-2886 | — | < 0.20.0 | 0.20.0 | Mar 27, 2025 | Missing validation of terminating delegation causes the client to continue searching the defined delegation list, even after searching a terminating delegation. This could cause the client to fetch a target from an incorrect source, altering the target contents. Users should upgr | ||
| CVE-2025-2885 | — | < 0.20.0 | 0.20.0 | Mar 27, 2025 | Missing validation of the root metatdata version number could allow an actor to supply an arbitrary version number to the client instead of the intended version in the root metadata file, altering the version fetched by the client. Users should upgrade to tough version 0.20.0 or | ||
| CVE-2021-41150 | — | < 0.12.0 | 0.12.0 | Oct 19, 2021 | Tough provides a set of Rust libraries and tools for using and generating the update framework (TUF) repositories. The tough library, prior to 0.12.0, does not properly sanitize delegated role names when caching a repository, or when loading a repository from the filesystem. When | ||
| CVE-2021-41149 | — | < 0.12.0 | 0.12.0 | Oct 19, 2021 | Tough provides a set of Rust libraries and tools for using and generating the update framework (TUF) repositories. The tough library, prior to 0.12.0, does not properly sanitize target names when caching a repository, or when saving specific targets to an output directory. When t | ||
| CVE-2020-15093 | — | < 0.7.1 | 0.7.1 | Jul 9, 2020 | The tough library (Rust/crates.io) prior to version 0.7.1 does not properly verify the threshold of cryptographic signatures. It allows an attacker to duplicate a valid signature in order to circumvent TUF requiring a minimum threshold of unique signatures before the metadata is |
- affected >= 0.9.0, < 0.22.0fixed 0.22.0
Missing expiration, hash, and length enforcement in delegated metadata validation in awslabs/tough before tough-v0.22.0 allows remote authenticated users with delegated signing authority to bypass TUF specification integrity checks for delegated targets metadata and poison the lo
- affected < 0.22.0fixed 0.22.0
Improper verification of cryptographic signature uniqueness in delegated role validation in awslabs/tough before tough-v0.22.0 allows remote authenticated users to bypass the TUF signature threshold requirement by duplicating a valid signature, causing the client to accept forged
- CVE-2025-2888Mar 27, 2025affected < 0.20.0fixed 0.20.0
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 t
- CVE-2025-2887Mar 27, 2025affected < 0.20.0fixed 0.20.0
During a target rollback, the client fails to detect the rollback for delegated targets. This could cause the client to fetch a target from an incorrect source, altering the target contents. Users should upgrade to tough version 0.20.0 or later and ensure any forked or derivative
- CVE-2025-2886Mar 27, 2025affected < 0.20.0fixed 0.20.0
Missing validation of terminating delegation causes the client to continue searching the defined delegation list, even after searching a terminating delegation. This could cause the client to fetch a target from an incorrect source, altering the target contents. Users should upgr
- CVE-2025-2885Mar 27, 2025affected < 0.20.0fixed 0.20.0
Missing validation of the root metatdata version number could allow an actor to supply an arbitrary version number to the client instead of the intended version in the root metadata file, altering the version fetched by the client. Users should upgrade to tough version 0.20.0 or
- CVE-2021-41150Oct 19, 2021affected < 0.12.0fixed 0.12.0
Tough provides a set of Rust libraries and tools for using and generating the update framework (TUF) repositories. The tough library, prior to 0.12.0, does not properly sanitize delegated role names when caching a repository, or when loading a repository from the filesystem. When
- CVE-2021-41149Oct 19, 2021affected < 0.12.0fixed 0.12.0
Tough provides a set of Rust libraries and tools for using and generating the update framework (TUF) repositories. The tough library, prior to 0.12.0, does not properly sanitize target names when caching a repository, or when saving specific targets to an output directory. When t
- CVE-2020-15093Jul 9, 2020affected < 0.7.1fixed 0.7.1
The tough library (Rust/crates.io) prior to version 0.7.1 does not properly verify the threshold of cryptographic signatures. It allows an attacker to duplicate a valid signature in order to circumvent TUF requiring a minimum threshold of unique signatures before the metadata is