{"answers":{"affected":"3 open source packages ship an affected version, including starkbank-ecdsa. It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-43572 in the wild and no public exploit code.","fix":"Upgrade starkbank-ecdsa to 2.0.1 or later.","what":"CVE-2021-43572 is a critical vulnerability in n/a, published on 9 Nov 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-43572 and fix it if it is affected.\n\nWhat it is: CVE-2021-43572 is a critical vulnerability in n/a, published on 9 Nov 2021. 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-2021-43572 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- starkbank-ecdsa (PyPI): affected all versions; fixed in 2.0.1\n- starkbank-ecdsa (PyPI): affected all versions; fixed in 2.0.1\n- starkbank-ecdsa (PyPI): affected all versions; fixed in 2.0.1\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-2021-43572/ (Markdown: https://insights.sbomify.com/CVE-2021-43572/index.md)","id":"CVE-2021-43572","markdown":"https://insights.sbomify.com/CVE-2021-43572/index.md","name":"CVE-2021-43572","record":{"aliases":["GHSA-92vm-mxjf-jqf3","PYSEC-2021-426"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Python ECDSA library","requires_auth":"none","summary":"Attackers can forge signatures on arbitrary messages due to missing non-zero checks in the Stark Bank Python ECDSA library.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"ecdsa-python","vendor":"starkbank"}],"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":"The verify function in the Stark Bank Python ECDSA library (aka starkbank-escada or ecdsa-python) before 2.0.1 fails to check that the signature is non-zero, which allows attackers to forge signatures on arbitrary messages.","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":"Improper Verification of Cryptographic Signature in starkbank-ecdsa","id":"CVE-2021-43572","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"other","year":"2021"},"n_packages":3,"n_references":3,"next":{"headline":"Memory corruption in n/a","id":"CVE-2021-43573"},"packages":[{"ecosystem":"PyPI","fixed":["2.0.1"],"introduced":["0"],"last_affected":[],"package":"starkbank-ecdsa","purl":null,"source":"GHSA-92vm-mxjf-jqf3"},{"ecosystem":"PyPI","fixed":["2.0.1"],"introduced":["0"],"last_affected":[],"package":"starkbank-ecdsa","purl":"pkg:pypi/starkbank-ecdsa","source":"GHSA-92vm-mxjf-jqf3"},{"ecosystem":"PyPI","fixed":["2.0.1"],"introduced":["0"],"last_affected":[],"package":"starkbank-ecdsa","purl":"pkg:pypi/starkbank-ecdsa","source":"PYSEC-2021-426"}],"prev":{"headline":"Improper Verification of Cryptographic Signature in starkbank-ecdsa","id":"CVE-2021-43571"},"products":["n/a"],"published":"2021-11-09","related":[],"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 forge signatures on arbitrary messages due to missing non-zero checks in the Stark Bank Python ECDSA library.","url":"https://insights.sbomify.com/CVE-2021-43572/"}