{"answers":{"affected":"1 open source package ship an affected version, including curl.","exploited":"There is no known exploitation of OSV-2022-139 in the wild and no public exploit code.","fix":"No fix has been published for OSV-2022-139 yet. Limit exposure of the affected software until one is available.","what":"OSV-2022-139 is an use after free vulnerability in curl, published on 11 Feb 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for OSV-2022-139 and fix it if it is affected.\n\nWhat it is: OSV-2022-139 is an use after free vulnerability in curl, published on 11 Feb 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of OSV-2022-139 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-2022-139/ (Markdown: https://insights.sbomify.com/OSV-2022-139/index.md)","id":"OSV-2022-139","markdown":"https://insights.sbomify.com/OSV-2022-139/index.md","name":"OSV-2022-139","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"HTTP/2 library","requires_auth":"none","summary":"A heap-use-after-free vulnerability in the nghttp2 library allows remote attackers to cause a denial of service or potentially execute arbitrary code.","user_interaction":"not_required","vuln_class":"use_after_free"},"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=44516\n\n```\nCrash type: Heap-use-after-free READ 4\nCrash state:\nnghttp2_http_record_request_method\nnghttp2_session_mem_send_internal\nnghttp2_session_send\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-use-after-free in nghttp2_http_record_request_method","id":"OSV-2022-139","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"OSS-Fuzz","product":null,"products":[],"type":"use_after_free","year":"2022"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"OSS-Fuzz","fixed":[],"introduced":[],"last_affected":[],"package":"curl","purl":"pkg:generic/curl","source":"OSV-2022-139"}],"products":null,"published":"2022-02-11","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-use-after-free vulnerability in the nghttp2 library allows remote attackers to cause a denial of service or potentially execute arbitrary code.","url":"https://insights.sbomify.com/OSV-2022-139/"}