{"answers":{"affected":"1 open source package ship an affected version, including cras.","exploited":"There is no known exploitation of OSV-2024-434 in the wild and no public exploit code.","fix":"No fix has been published for OSV-2024-434 yet. Limit exposure of the affected software until one is available.","what":"OSV-2024-434 is a vulnerability in cras, published on 5 May 2024. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for OSV-2024-434 and fix it if it is affected.\n\nWhat it is: OSV-2024-434 is a vulnerability in cras, published on 5 May 2024. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of OSV-2024-434 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- cras (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-2024-434/ (Markdown: https://insights.sbomify.com/OSV-2024-434/index.md)","id":"OSV-2024-434","markdown":"https://insights.sbomify.com/OSV-2024-434/index.md","name":"OSV-2024-434","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Bluetooth validation library","requires_auth":"none","summary":"An attacker can trigger a denial of service via a use-of-uninitialized-value bug in Bluetooth device address validation.","user_interaction":"not_required","vuln_class":"other"},"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=68420\n\n```\nCrash type: Use-of-uninitialized-value\nCrash state:\nvalidate_bluetooth_device_address\nhandle_on_bluetooth_device_added\nfuzzer_on_bluetooth_device_added\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":"Use-of-uninitialized-value in validate_bluetooth_device_address","id":"OSV-2024-434","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"OSS-Fuzz","product":null,"products":[],"type":"other","year":"2024"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"OSS-Fuzz","fixed":[],"introduced":[],"last_affected":[],"package":"cras","purl":"pkg:generic/cras","source":"OSV-2024-434"}],"products":null,"published":"2024-05-05","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 attacker can trigger a denial of service via a use-of-uninitialized-value bug in Bluetooth device address validation.","url":"https://insights.sbomify.com/OSV-2024-434/"}