{"answers":{"affected":"3 open source packages ship an affected version, including tuf. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-6174 in the wild and no public exploit code.","fix":"Upgrade tuf to 0.12.2 or later.","what":"CVE-2020-6174 is a critical vulnerability in n/a, published on 5 Feb 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-6174 and fix it if it is affected.\n\nWhat it is: CVE-2020-6174 is a critical vulnerability in n/a, published on 5 Feb 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-6174 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- tuf (PyPI): affected all versions; fixed in 0.12.2\n- tuf (PyPI): affected all versions; fixed in 0.12.2\n- tuf (PyPI): affected all versions; fixed in 0.12.2\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-2020-6174/ (Markdown: https://insights.sbomify.com/CVE-2020-6174/index.md)","id":"CVE-2020-6174","markdown":"https://insights.sbomify.com/CVE-2020-6174/index.md","name":"CVE-2020-6174","record":{"aliases":["GHSA-pwqf-9h7j-7mv8","PYSEC-2020-147"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"TUF Python library","requires_auth":"none","summary":"Attackers can bypass cryptographic signature verification in the TUF library, potentially allowing the installation of malicious software updates.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"the_update_framework","vendor":"linuxfoundation"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"}],"description":"TUF (aka The Update Framework) through 0.12.1 has Improper Verification of a Cryptographic Signature.","ecosystems":["PyPI"],"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":"Incorrect threshold signature computation in TUF","id":"CVE-2020-6174","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"weak_cryptography","year":"2020"},"n_packages":3,"n_references":1,"next":{"headline":"Security feature bypass in n/a","id":"CVE-2020-6175"},"packages":[{"ecosystem":"PyPI","fixed":["0.12.2"],"introduced":["0"],"last_affected":[],"package":"tuf","purl":null,"source":"GHSA-pwqf-9h7j-7mv8"},{"ecosystem":"PyPI","fixed":["0.12.2"],"introduced":["0"],"last_affected":[],"package":"tuf","purl":"pkg:pypi/tuf","source":"GHSA-pwqf-9h7j-7mv8"},{"ecosystem":"PyPI","fixed":["0.12.2"],"introduced":["0"],"last_affected":[],"package":"tuf","purl":"pkg:pypi/tuf","source":"PYSEC-2020-147"}],"prev":{"headline":"Client Denial of Service on TUF","id":"CVE-2020-6173"},"products":["n/a"],"published":"2020-02-05","related":[{"cvss_score":8.7,"headline":"Invalid root may become trusted root in The Update Framework (TUF)","id":"CVE-2020-15163","kev_date_added":null,"published":"2020-09-09"},{"cvss_score":7.5,"headline":"Client metadata path-traversal in python-tuf","id":"CVE-2021-41131","kev_date_added":null,"published":"2021-10-19"},{"cvss_score":5.3,"headline":"Client Denial of Service on TUF","id":"CVE-2020-6173","kev_date_added":null,"published":"2020-01-14"}],"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":"PyPA Advisory Database","prefix":"PYSEC"},{"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Attackers can bypass cryptographic signature verification in the TUF library, potentially allowing the installation of malicious software updates.","url":"https://insights.sbomify.com/CVE-2020-6174/"}