{"answers":{"affected":"1 open source package ship an affected version, including boost.","exploited":"There is no known exploitation of OSV-2018-417 in the wild and no public exploit code.","fix":"No fix has been published for OSV-2018-417 yet. Limit exposure of the affected software until one is available.","what":"OSV-2018-417 is a memory corruption vulnerability in boost, published on 15 Jan 2021."},"fix_prompt":"Check this codebase for OSV-2018-417 and fix it if it is affected.\n\nWhat it is: OSV-2018-417 is a memory corruption vulnerability in boost, published on 15 Jan 2021. \nExploitation: There is no known exploitation of OSV-2018-417 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- boost (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-2018-417/ (Markdown: https://insights.sbomify.com/OSV-2018-417/index.md)","id":"OSV-2018-417","markdown":"https://insights.sbomify.com/OSV-2018-417/index.md","name":"OSV-2018-417","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"unknown","non_default_config":false,"product_category":"Boost C++ library","requires_auth":"none","summary":"An unknown read vulnerability in Boost regex matching can cause application crashes, requiring a patch to ensure stability.","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=9539\n\n```\nCrash type: UNKNOWN READ\nCrash state:\nboost::sub_match\u003cstd::__1::__wrap_iter\u003cchar const*\u003e \u003e::sub_match\n_ZNSt3__16vectorIN5boost9sub_matchINS_11__wrap_iterIPKcEEEENS_9allocatorIS7_EEE1\nboost::match_results\u003cstd::__1::__wrap_iter\u003cchar const*\u003e, std::__1::allocator\u003cboo\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":"UNKNOWN READ in boost::sub_match\u003cstd::__1::__wrap_iter\u003cchar const*\u003e \u003e::sub_match","id":"OSV-2018-417","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":"boost","purl":"pkg:generic/boost","source":"OSV-2018-417"}],"products":null,"published":"2021-01-15","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":"An unknown read vulnerability in Boost regex matching can cause application crashes, requiring a patch to ensure stability.","url":"https://insights.sbomify.com/OSV-2018-417/"}