CVE-2020-15093High· 8.6▾ TwilightImproper uniqueness verification of signature threshold
▾ Twilight zone — High severity, or a signal on a lesser flaw
impact 47.3 · likelihood 0.3 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Exploit-prediction probability, daily snapshots since Jul 31.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via OSV
1.4%
Last analysed / modified upstream
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.
A fix is available in version 0.7.1.
CVE-2020-6174 is assigned to the same issue in the TUF reference implementation.
If you have any questions or comments about this advisory, contact AWS Security at [email protected].
tough >= 0.0.0-0, < 0.7.1Upgrade to a patched release:
tough 0.7.1Connected by shared product, vendor, weakness, or advisory.
CVE-2021-41149High· 8.2Improper sanitization of target names
CVE-2026-6966Medium· 5.3Signature Threshold Bypass in awslabs/tough Delegated Roles
CVE-2026-6967Medium· 5.9Missing Delegated Metadata Validation in awslabs/tough
CVE-2026-6968Medium· 5.9Multiple Path Traversal Variants in awslabs/tough