{"answers":{"affected":"1 open source package ship an affected version, including json.","exploited":"There is no known exploitation of OSV-2022-425 in the wild and no public exploit code.","fix":"No fix has been published for OSV-2022-425 yet. Limit exposure of the affected software until one is available.","what":"OSV-2022-425 is an use after free vulnerability in json, published on 21 May 2022."},"fix_prompt":"Check this codebase for OSV-2022-425 and fix it if it is affected.\n\nWhat it is: OSV-2022-425 is an use after free vulnerability in json, published on 21 May 2022. \nExploitation: There is no known exploitation of OSV-2022-425 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- json (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-425/ (Markdown: https://insights.sbomify.com/OSV-2022-425/index.md)","id":"OSV-2022-425","markdown":"https://insights.sbomify.com/OSV-2022-425/index.md","name":"OSV-2022-425","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service","code_execution"],"network_reachable":"unknown","non_default_config":false,"product_category":"nlohmann JSON library","requires_auth":"none","summary":"A heap-use-after-free vulnerability in the nlohmann JSON library allows attackers to cause crashes or potentially execute arbitrary code via crafted input.","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=47533\n\n```\nCrash type: Heap-use-after-free READ 1\nCrash state:\nstd::__1::__tree_node_base\u003cvoid*\u003e*\u0026 std::__1::__tree\u003cstd::__1::__value_type\u003cstd:\nstd::__1::pair\u003cstd::__1::__tree_iterator\u003cstd::__1::__value_type\u003cstd::__1::basic_\nnlohmann::detail::binary_reader\u003cnlohmann::basic_json\u003cstd::__1::map, std::__1::ve\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 std::__1::__tree_node_base\u003cvoid*\u003e*\u0026 std::__1::__tree\u003cstd::__1::__value_type\u003cstd:","id":"OSV-2022-425","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":"json","purl":"pkg:generic/json","source":"OSV-2022-425"}],"products":null,"published":"2022-05-21","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 nlohmann JSON library allows attackers to cause crashes or potentially execute arbitrary code via crafted input.","url":"https://insights.sbomify.com/OSV-2022-425/"}