{"answers":{"affected":"1 open source package ship an affected version, including curl.","exploited":"There is no known exploitation of OSV-2021-1629 in the wild and no public exploit code.","fix":"No fix has been published for OSV-2021-1629 yet. Limit exposure of the affected software until one is available.","what":"OSV-2021-1629 is a memory corruption vulnerability in curl, published on 27 Nov 2021. It can be exploited over the network, with no action from the victim."},"fix_prompt":"Check this codebase for OSV-2021-1629 and fix it if it is affected.\n\nWhat it is: OSV-2021-1629 is a memory corruption vulnerability in curl, published on 27 Nov 2021. It can be exploited over the network, with no action from the victim.\nExploitation: There is no known exploitation of OSV-2021-1629 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- curl (OSS-Fuzz): affected all versions; no fix listed\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/OSV-2021-1629/ (Markdown: https://insights.sbomify.com/OSV-2021-1629/index.md)","id":"OSV-2021-1629","markdown":"https://insights.sbomify.com/OSV-2021-1629/index.md","name":"OSV-2021-1629","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"cURL library","requires_auth":"unknown","summary":"A heap-buffer-overflow in cURL's SASL mechanism decoding can lead to crashes or potential code execution when processing malicious URLs.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=41403\n\n```\nCrash type: Heap-buffer-overflow READ 10\nCrash state:\nCurl_sasl_decode_mech\nCurl_sasl_parse_url_auth_option\nsmtp_parse_url_options\n```","ecosystems":["OSS-Fuzz"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":false,"headline":"Heap-buffer-overflow in Curl_sasl_decode_mech","id":"OSV-2021-1629","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"OSS-Fuzz","product":null,"products":[],"type":"memory_corruption","year":"2021"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"OSS-Fuzz","fixed":[],"introduced":[],"last_affected":[],"package":"curl","purl":"pkg:generic/curl","source":"OSV-2021-1629"}],"products":null,"published":"2021-11-27","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"OSS-Fuzz","prefix":"OSV"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"A heap-buffer-overflow in cURL's SASL mechanism decoding can lead to crashes or potential code execution when processing malicious URLs.","url":"https://insights.sbomify.com/OSV-2021-1629/"}