Most recent entries from all

certfr-2025-avi-0622 — De multiples vulnérabilités ont été découvertes dans les produits VMware. Certaines d'entre elles permettent à un attaq…

2026-10-03T07:05:11.645612+00:00

certfr-2025-avi-0622

EUVD-2026-234179

2026-10-03T07:05:11.645654+00:00

EUVD-2026-234179

fkie_cve-2022-29173

2026-10-03T07:05:11.645670+00:00

go-tuf is a Go implementation of The Update Framework (TUF). go-tuf does not correctly implement the client workflow for updating the metadata files for roles other than the root role. Specifically, checks for rollback attacks are not implemented correctly meaning an attacker can cause clients to install software that is older than the software which the client previously knew to be available, and may include software with known vulnerabilities. In more detail, the client code of go-tuf has several issues in regards to preventing rollback attacks: 1. It does not take into account the content of any previously trusted metadata, if available, before proceeding with updating roles other than the root role (i.e., steps 5.4.3.1 and 5.5.5 of the detailed client workflow). This means that any form of version verification done on the newly-downloaded metadata is made using the default value of zero, which always passes. 2. For both timestamp and snapshot roles, go-tuf saves these metadata files as trusted before verifying if the version of the metafiles they refer to is correct (i.e., steps 5.5.4 and 5.6.4 of the detailed client workflow). A fix is available in version 0.3.0 or newer. No workarounds are known for this issue apart from upgrading.

GHSA-66x3-6cw3-v5gj — Improper Validation of Integrity Check Value in go-tuf

2026-10-03T07:05:11.645705+00:00

Affected: Go: github.com/theupdateframework/go-tuf

### Impact

[go-tuf](https://github.com/theupdateframework/go-tuf) does not correctly implement the [client workflow](https://theupdateframework.github.io/specification/v1.0.28/index.html#detailed-client-workflow) for updating the metadata files for roles other than the root role. Specifically, checks for rollback attacks are not implemented correctly meaning an attacker can cause clients to install software that is older than the software which the client previously knew to be available, and may include software with known vulnerabilities.

In more detail, the client code of go-tuf has several issues in regards to preventing rollback attacks: 1. It does not take into account the content of any previously trusted metadata, if available, before proceeding with updating roles other than the root role (i.e., steps 5.4.3.1 and 5.5.5 of the detailed client workflow). This means that any form of version verification done on the newly-downloaded metadata is made using the default value of zero, which always passes. 1. For both timestamp and snapshot roles, go-tuf saves these metadata files as trusted before verifying if the version of the metafiles they refer to is correct (i.e., steps 5.5.4 and 5.6.4 of the detailed client workflow).

### Patches

A fix is available in version 0.3.0 or newer.

### Workarounds

No workarounds are known for this issue apart from upgrading.

### References

* Commit resolving the issue https://github.com/theupdateframework/go-tuf/commit/ed6788e710fc…

gsd-2022-29173

2026-10-03T07:05:11.645752+00:00

gsd-2022-29173

RHSA-2022:5704 — Red Hat Security Advisory: ACS 3.71 enhancement and security update

2026-10-03T07:05:11.645765+00:00

go-tuf: No protection against rollback attacks for roles other than root