{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-36877 exists.","fix":"No fix has been published for CVE-2024-36877 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-36877 is a high-severity memory corruption vulnerability in n/a, published on 12 Aug 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-36877 and fix it if it is affected.\n\nWhat it is: CVE-2024-36877 is a high-severity memory corruption vulnerability in n/a, published on 12 Aug 2024. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-36877 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-36877/ (Markdown: https://insights.sbomify.com/CVE-2024-36877/index.md)","id":"CVE-2024-36877","markdown":"https://insights.sbomify.com/CVE-2024-36877/index.md","name":"CVE-2024-36877","record":{"aliases":["GHSA-7j43-4jvq-vg4w"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"MSI motherboard firmware","requires_auth":"high_privilege","summary":"Attackers can exploit a write-what-where condition in MSI motherboard firmware to execute arbitrary code and escalate privileges.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":8.2,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-123","name":"Write-what-where Condition"}],"description":"Micro-Star International Z-series motherboards (Z590, Z490, and Z790) and B-series motherboards (B760, B560, B660, and B460) with firmware 7D25v14, 7D25v17 to 7D25v19, and 7D25v1A to 7D25v1H was discovered to contain a write-what-where condition in the in the SW handler for SMI 0xE3. Motherboard's with the following chipsets are affected: Intel 300, Intel 400, Intel 500, Intel 600, Intel 700, AMD 300, AMD 400, AMD 500, AMD 600 and AMD 700.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2024-08-09","github_poc":2,"max_poc_stars":47,"metasploit":0,"nuclei":0,"refs":[{"date":"2024-08-09T15:33:04Z","kind":"github_poc","ref":"https://github.com/jjensn/CVE-2024-36877","stars":47,"title":"Exploit POC for CVE-2024-36877"},{"date":"2024-08-17T20:47:52Z","kind":"github_poc","ref":"https://github.com/CERTologists/POC-CVE-2024-36877","stars":0,"title":null}],"tier":"weaponised"},"has_fix":null,"headline":"Memory corruption in n/a","id":"CVE-2024-36877","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Bluetooth: qca: add missing firmware sanity checks","id":"CVE-2024-36880"},"packages":[],"prev":{"headline":"Jan path traversal vulnerability","id":"CVE-2024-36858"},"products":["n/a"],"published":"2024-08-12","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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-03-13","vendors":["n/a"]},"summary":"Attackers can exploit a write-what-where condition in MSI motherboard firmware to execute arbitrary code and escalate privileges.","url":"https://insights.sbomify.com/CVE-2024-36877/"}