{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-45434 exists.","fix":"No fix has been published for CVE-2024-45434 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-45434 is a critical use after free vulnerability in n/a, published on 12 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-45434 and fix it if it is affected.\n\nWhat it is: CVE-2024-45434 is a critical use after free vulnerability in n/a, published on 12 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-45434 exists.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\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/CVE-2024-45434/ (Markdown: https://insights.sbomify.com/CVE-2024-45434/index.md)","id":"CVE-2024-45434","markdown":"https://insights.sbomify.com/CVE-2024-45434/index.md","name":"CVE-2024-45434","record":{"aliases":["GHSA-gfw9-vqj5-5mg2"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Bluetooth stack library","requires_auth":"none","summary":"A use-after-free flaw in the BlueSDK Bluetooth stack allows attackers to achieve remote code execution within the user account context.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"blue_sdk","vendor":"opensynergy"}],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-416","name":"Use After Free"}],"description":"OpenSynergy BlueSDK (aka Blue SDK) through 6.x has a Use-After-Free. The specific flaw exists within the BlueSDK Bluetooth stack. The issue results from the lack of validating the existence of an object before performing operations on the object (aka use after free). An attacker can leverage this to achieve remote code execution in the context of a user account under which the Bluetooth process runs.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Use after free in n/a","id":"CVE-2024-45434","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Other in n/a","id":"CVE-2024-45435"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2024-45433"},"products":["n/a"],"published":"2025-09-12","related":[{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2024-45432","kev_date_added":null,"published":"2025-09-12"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2018-20378","kev_date_added":null,"published":"2019-03-29"},{"cvss_score":6.5,"headline":"Security feature bypass in n/a","id":"CVE-2024-45433","kev_date_added":null,"published":"2025-09-12"},{"cvss_score":5.3,"headline":"Other in n/a","id":"CVE-2024-45431","kev_date_added":null,"published":"2025-09-12"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-09-12","vendors":["n/a"]},"summary":"A use-after-free flaw in the BlueSDK Bluetooth stack allows attackers to achieve remote code execution within the user account context.","url":"https://insights.sbomify.com/CVE-2024-45434/"}