{"answers":{"affected":"3 open source packages ship an affected version, including github.com/theupdateframework/go-tuf. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-29173 in the wild and no public exploit code.","fix":"Upgrade github.com/theupdateframework/go-tuf to 0.3.0 or later.","what":"CVE-2022-29173 is a high-severity vulnerability in theupdateframework go-tuf, published on 5 May 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2022-29173 and fix it if it is affected.\n\nWhat it is: CVE-2022-29173 is a high-severity vulnerability in theupdateframework go-tuf, published on 5 May 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2022-29173 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/theupdateframework/go-tuf (Go): affected all versions; fixed in 0.3.0\n- github.com/theupdateframework/go-tuf (Go): affected all versions; fixed in 0.3.0\n- github.com/theupdateframework/go-tuf (Go): affected all versions; fixed in 0.3.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2022-29173/ (Markdown: https://insights.sbomify.com/CVE-2022-29173/index.md)","id":"CVE-2022-29173","markdown":"https://insights.sbomify.com/CVE-2022-29173/index.md","name":"CVE-2022-29173","record":{"aliases":["GHSA-66x3-6cw3-v5gj","GO-2022-0444"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Go TUF library","requires_auth":"low_privilege","summary":"Attackers can force clients to install older, vulnerable software by bypassing rollback protections in the go-tuf library.","user_interaction":"required","vuln_class":"supply_chain"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"go-tuf","vendor":"theupdateframework"}],"cvss":{"score":8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-354","name":"Improper Validation of Integrity Check Value"}],"description":"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.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"No protection against rollback attacks in go-tuf","id":"CVE-2022-29173","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"supply_chain","year":"2022"},"n_packages":3,"n_references":2,"next":{"headline":"Predictable password reset token may lead to account takeover in countly-server","id":"CVE-2022-29174"},"packages":[{"ecosystem":"Go","fixed":["0.3.0"],"introduced":["0"],"last_affected":[],"package":"github.com/theupdateframework/go-tuf","purl":null,"source":"GHSA-66x3-6cw3-v5gj"},{"ecosystem":"Go","fixed":["0.3.0"],"introduced":["0"],"last_affected":[],"package":"github.com/theupdateframework/go-tuf","purl":"pkg:golang/github.com/theupdateframework/go-tuf","source":"GHSA-66x3-6cw3-v5gj"},{"ecosystem":"Go","fixed":["0.3.0"],"introduced":["0"],"last_affected":[],"package":"github.com/theupdateframework/go-tuf","purl":"pkg:golang/github.com/theupdateframework/go-tuf","source":"GO-2022-0444"}],"prev":{"headline":"HTML injection with additional signup fields","id":"CVE-2022-29172"},"products":["go-tuf"],"published":"2022-05-05","related":[{"cvss_score":5.9,"headline":"go-tuf affected by client DoS via malformed server response","id":"CVE-2026-23991","kev_date_added":null,"published":"2026-01-22"},{"cvss_score":5.9,"headline":"go-tuf improperly validates the configured threshold for delegations","id":"CVE-2026-23992","kev_date_added":null,"published":"2026-01-22"},{"cvss_score":4.7,"headline":"go-tuf Path Traversal in TAP 4 Multirepo Client Allows Arbitrary File Write via Malicious Repository Names","id":"CVE-2026-24686","kev_date_added":null,"published":"2026-01-27"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-04-23","vendors":["theupdateframework"]},"summary":"Attackers can force clients to install older, vulnerable software by bypassing rollback protections in the go-tuf library.","url":"https://insights.sbomify.com/CVE-2022-29173/"}