Advisory

GHSA-5q2r-92f9-4m49

Also known as: CVE-2020-15093, RUSTSEC-2020-0024

Summary

Improper verification of signature threshold in tough

Details

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 at [[email protected]](mailto:[email protected]).

Severity

High Basis: The source's own band: HIGH

Dates

Published
2021-08-25 20:56 UTC
Modified
2026-07-08 06:29 UTC

Affected packages and fixes

tough

crates.io · All systems

Affected

  • introduced 0, fixed 0.7.1 (semver)

Fixed versions

0.7.1

Fix

  • Fixed version 0.7.1
    cargo update -p tough --precise 0.7.1

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences