{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2024-31955 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-31955 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-31955 is a medium-severity vulnerability in n/a, published on 15 Oct 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-31955 and fix it if it is affected.\n\nWhat it is: CVE-2024-31955 is a medium-severity vulnerability in n/a, published on 15 Oct 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-31955 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-31955/ (Markdown: https://insights.sbomify.com/CVE-2024-31955/index.md)","id":"CVE-2024-31955","markdown":"https://insights.sbomify.com/CVE-2024-31955/index.md","name":"CVE-2024-31955","record":{"aliases":["GHSA-8h4j-cm33-q84h"],"analysis":{"component_type":"hardware_firmware","fix_type":"no_fix_stated","impacts":["security_bypass","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Samsung eMMC firmware","requires_auth":"none","summary":"Attackers can bypass authentication to write to protected memory in Samsung eMMC firmware using electromagnetic fault injection.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":4.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AC:H/AV:P/A:N/C:N/I:H/PR:N/S:C/UI:N","version":"3.1"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"An issue was discovered in Samsung eMMC with KLMAG2GE4A and KLM8G1WEMB firmware. Code bypass through Electromagnetic Fault Injection allows an attacker to successfully authenticate and write to the RPMB (Replay Protected Memory Block) area without possessing secret information.","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":"Security feature bypass in n/a","id":"CVE-2024-31955","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in n/a","id":"CVE-2024-31956"},"packages":[],"prev":{"headline":"Privilege escalation in n/a","id":"CVE-2024-31954"},"products":["n/a"],"published":"2024-10-15","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-10-30","vendors":["n/a"]},"summary":"Attackers can bypass authentication to write to protected memory in Samsung eMMC firmware using electromagnetic fault injection.","url":"https://insights.sbomify.com/CVE-2024-31955/"}