GHSA-66x3-6cw3-v5gj
HIGHGHSA-66x3-6cw3-v5gj is a high-severity (CVSS 8) CWE-354 vulnerability in github.com/theupdateframework/go-tuf. O3 Security confirms whether GHSA-66x3-6cw3-v5gj is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Improper Validation of Integrity Check Value in go-tuf
Blast Radius
github.com/theupdateframework/go-tufReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Impact
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:
- 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.
- 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/ed6788e710fc3093a7ecc2d078bf734c0f200d8d
- TUF specification version against which this vulnerability is observed is v.1.0.28. For more details, refer to Section 5.
- Codebase that is affected is go-tuf@f0c3294f63b9145029464164f9bce49553b77cbb
For more information
If you have any questions or comments about this advisory:
- Open an issue in go-tuf
- Email us at TUF's mailing list
- The #tuf channel on CNCF Slack.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/theupdateframework/go-tuf | all versions | 0.3.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/theupdateframework/go-tuf. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/theupdateframework/go-tuf to 0.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-66x3-6cw3-v5gj is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-66x3-6cw3-v5gj is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-66x3-6cw3-v5gj. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-66x3-6cw3-v5gj in your dependencies?
O3 detects GHSA-66x3-6cw3-v5gj across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.