{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2024-29149 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-29149 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-29149 is a high-severity vulnerability in n/a, published on 7 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 CVE-2024-29149 and fix it if it is affected.\n\nWhat it is: CVE-2024-29149 is a high-severity vulnerability in n/a, published on 7 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 CVE-2024-29149 in the wild and no public exploit code.\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-29149/ (Markdown: https://insights.sbomify.com/CVE-2024-29149/index.md)","id":"CVE-2024-29149","markdown":"https://insights.sbomify.com/CVE-2024-29149/index.md","name":"CVE-2024-29149","record":{"aliases":["GHSA-4g7f-972r-hmcv"],"analysis":{"component_type":"iot_embedded","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Alcatel-Lucent deskphones","requires_auth":"low_privilege","summary":"An authenticated attacker can replace verified firmware with malicious code during updates due to a race condition, leading to arbitrary code execution on Alcatel-Lucent deskphones.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":7.4,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:P/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-367","name":"Time-of-check Time-of-use (TOCTOU) Race Condition"}],"description":"An issue was discovered in Alcatel-Lucent ALE NOE deskphones through 86x8_NOE-R300.1.40.12.4180 and SIP deskphones through 86x8_SIP-R200.1.01.10.728. Because of a time-of-check time-of-use vulnerability, an authenticated attacker is able to replace the verified firmware image with malicious firmware during the update process.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Race condition in n/a","id":"CVE-2024-29149","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Privilege escalation in n/a","id":"CVE-2024-29150"},"packages":[],"prev":{"headline":"Information disclosure in Multiple MFPs (multifunction printers)","id":"CVE-2024-29146"},"products":["n/a"],"published":"2024-05-07","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-02","vendors":["n/a"]},"summary":"An authenticated attacker can replace verified firmware with malicious code during updates due to a race condition, leading to arbitrary code execution on Alcatel-Lucent deskphones.","url":"https://insights.sbomify.com/CVE-2024-29149/"}