Most recent entries from all

EUVD-2026-37234

fkie_cve-2020-6174

TUF (aka The Update Framework) through 0.12.1 has Improper Verification of a Cryptographic Signature.

GHSA-pwqf-9h7j-7mv8 — Incorrect threshold signature computation in TUF

Affected: PyPI: tuf

### Impact Metadadata signature verification, as used in `tuf.client.updater`, counted each of multiple signatures with identical authorized keyids separately towards the threshold. Therefore, an attacker with access to a valid signing key could create multiple valid signatures in order to meet the minimum threshold of keys before the metadata was considered valid.

The tuf maintainers would like to thank Erik MacLean of Analog Devices, Inc. for reporting this issue.

### Patches A [fix](https://github.com/theupdateframework/tuf/pull/974) is available in version [0.12.2](https://github.com/theupdateframework/tuf/releases/tag/v0.12.2) or newer.

### Workarounds No workarounds are known for this issue.

### References * [CVE-2020-6174](https://nvd.nist.gov/vuln/detail/CVE-2020-6174) * Pull request resolving the issue [PR 974](https://github.com/theupdateframework/tuf/pull/974)

gsd-2020-6174

PYSEC-2020-147

Affected: PyPI: tuf

TUF (aka The Update Framework) through 0.12.1 has Improper Verification of a Cryptographic Signature.

RUSTSEC-2020-0024 — Improper uniqueness verification of signature threshold

Affected: crates.io: tough

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 aws-security@amazon.com.