Loading...
Skip to main content
GeekWala

CVE-2020-15093 — Vulnerability in tough — CVE Details

HIGH

Improper verification of signature threshold in tough

Published August 25, 2021Updated July 8, 2026Source: osv

Summary

## Impact The tough library, prior to 0.7.1, does not properly verify the uniqueness of keys in the signatures provided to meet the threshold of cryptographic signatures. It allows someone with access to a valid signing key to create multiple valid signatures in order to circumvent TUF requiring a minimum threshold of unique keys before the metadata is considered valid. AWS would like to thank Erick Tryzelaar of the Google Fuchsia Team for reporting this issue. ## Patches A fix is available in version 0.7.1. ## Workarounds No workarounds to this issue are known. ## References CVE-2020-6174 is assigned to the same issue in the TUF reference implementation. https://github.com/theupdateframework/tuf/pull/974 https://nvd.nist.gov/vuln/detail/CVE-2020-6174 ## For more information If you have any questions or comments about this advisory, [contact AWS Security](https://aws.amazon.com/security/vulnerability-reporting/) at [aws-security@amazon.com](mailto:aws-security@amazon.com).

Advisory Timeline

  • First published August 25, 2021 (1874 days ago).
  • Last revised July 8, 2026 — 1777 days after initial publication.

Remediation

Upgrade to the fixed version using your package manager.

Cargo
Update tough to 0.7.1 or later
cargo update -p tough --precise 0.7.1

After upgrading, run your dependency scanner again to confirm the vulnerability is resolved.

Affected Packages (1)

Affects 1 ecosystem: crates.io (1).

PackageEcosystemAffectedFixed In
tough
crates.io
All versions0.7.1

Vulnerability Classification

Common Weakness Enumeration (CWE) identifiers for this vulnerability type.

  • CWE-347
    Improper Verification of Cryptographic SignatureMITRE

CVSS Score Breakdown

What the CVSS (Common Vulnerability Scoring System) 8.6 score means for each attack dimension.

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Changed
Confidentiality
None
Integrity
High
Availability
None

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

References

Frequently Asked Questions

What is CVE-2020-15093?
Improper verification of signature threshold in tough This vulnerability has been assigned a severity rating of HIGH (CVSS score: 8.6/10).
How do I check if my project is affected by CVE-2020-15093?
CVE-2020-15093 affects tough. Use GeekWala's free vulnerability scanner to check your dependencies against CVE-2020-15093 and 200,000+ other known vulnerabilities.

Severity & Exploitability

CVSS Score
8.6

High exploitability or significant impact. Prioritize remediation within days.

Also Known As

GHSA-5q2r-92f9-4m49
RUSTSEC-2020-0024

Related CVEs

  • CVE-2026-6967
    HIGH

    awslabs/tough is Missing Delegated Metadata Validation

  • CVE-2026-93657
    HIGH

    hickory-resolver: Resolver::lookup() and Resolver::lookup_ip() APIs obscure DNSSEC validation failures

  • CVE-2026-18140
    HIGH

    aws-smithy-json: Uncontrolled recursion in the aws-smithy-json unknown-key skip path allows unauthenticated remote denial of service in smithy-rs generated servers

  • CVE-2021-41150
    HIGH

    Improper sanitization of delegated role names

  • CVE-2021-41149
    HIGH

    Improper sanitization of target names

More crates.io advisories

Check if you're affected

Scan your dependencies to see if this vulnerability affects your projects.

Scan Your Dependencies