{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2024-10238 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-10238 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-10238 is a high-severity memory corruption vulnerability in SMCI MBD-X12DPG-OA6, published on 4 Feb 2025. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-10238 and fix it if it is affected.\n\nWhat it is: CVE-2024-10238 is a high-severity memory corruption vulnerability in SMCI MBD-X12DPG-OA6, published on 4 Feb 2025. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-10238 in the wild and no public exploit code.\n\nAffected product: SMCI MBD-X12DPG-OA6. 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-10238/ (Markdown: https://insights.sbomify.com/CVE-2024-10238/index.md)","id":"CVE-2024-10238","markdown":"https://insights.sbomify.com/CVE-2024-10238/index.md","name":"CVE-2024-10238","record":{"aliases":["GHSA-6rpv-x4qm-m5rx"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Supermicro server firmware","requires_auth":"high_privilege","summary":"An attacker can cause a stack overflow and potentially execute code by uploading a specially crafted firmware image to Supermicro server hardware.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Supermicro","cpe":[],"cvss":{"score":7.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-121","name":"Stack-based Buffer Overflow"}],"description":"A security issue in the firmware image verification implementation \n\n at Supermicro MBD-X12DPG-OA6. An attacker can upload a specially crafted image that will cause a stack overflow is caused by not checking fld-\u003eused_bytes.","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":"fld-\u003eused_bytes without sanity check causes stack overflow","id":"CVE-2024-10238","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"fld-\u003eused_bytes without sanity check causes stack overflow","id":"CVE-2024-10239"},"packages":[],"prev":{"headline":"SMC BMC Firmware Image Authentication Design Issue","id":"CVE-2024-10237"},"products":["MBD-X12DPG-OA6"],"published":"2025-02-04","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":"total"},"state":"PUBLISHED","updated":"2025-02-04","vendors":["SMCI"]},"summary":"An attacker can cause a stack overflow and potentially execute code by uploading a specially crafted firmware image to Supermicro server hardware.","url":"https://insights.sbomify.com/CVE-2024-10238/"}