{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-47252 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-47252 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-47252 is a medium-severity memory corruption vulnerability in n/a, published on 26 Apr 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-2023-47252 and fix it if it is affected.\n\nWhat it is: CVE-2023-47252 is a medium-severity memory corruption vulnerability in n/a, published on 26 Apr 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-2023-47252 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-2023-47252/ (Markdown: https://insights.sbomify.com/CVE-2023-47252/index.md)","id":"CVE-2023-47252","markdown":"https://insights.sbomify.com/CVE-2023-47252/index.md","name":"CVE-2023-47252","record":{"aliases":["GHSA-46ff-m72j-q8vp"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["data_modify","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"InsydeH2O BIOS","requires_auth":"low_privilege","summary":"Attackers can tamper with SMM communication buffers via out-of-bounds access in InsydeH2O firmware, potentially modifying data or escalating privileges.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"kernel","vendor":"insyde"}],"cvss":{"score":6.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"An issue was discovered in PnpSmm in Insyde InsydeH2O with kernel 5.0 through 5.6. There is a possible out-of-bounds access in the SMM communication buffer, leading to tampering. The PNP-related SMI sub-functions do not verify data size before getting it from the communication buffer, which could lead to possible circumstances where the data immediately following the command buffer could be destroyed with a fixed value. This is fixed in kernel 5.2 v05.28.45, kernel 5.3 v05.37.45, kernel 5.4 v05.45.45, kernel 5.5 v05.53.45, and kernel 5.6 v05.60.45.","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":"Memory corruption in n/a","id":"CVE-2023-47252","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"Code injection in n/a","id":"CVE-2023-47253"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2023-47251"},"products":["n/a"],"published":"2024-04-26","related":[{"cvss_score":8.2,"headline":"Memory corruption in n/a","id":"CVE-2022-36337","kev_date_added":null,"published":"2022-11-23"},{"cvss_score":8.2,"headline":"Privilege escalation in n/a","id":"CVE-2022-29275","kev_date_added":null,"published":"2022-11-15"},{"cvss_score":8.2,"headline":"Memory corruption in n/a","id":"CVE-2022-29276","kev_date_added":null,"published":"2022-11-15"},{"cvss_score":8.2,"headline":"Memory corruption in n/a","id":"CVE-2022-29278","kev_date_added":null,"published":"2022-11-15"},{"cvss_score":8.2,"headline":"Memory corruption in n/a","id":"CVE-2022-29279","kev_date_added":null,"published":"2022-11-15"},{"cvss_score":8.2,"headline":"Memory corruption in n/a","id":"CVE-2022-30771","kev_date_added":null,"published":"2022-11-15"},{"cvss_score":8.2,"headline":"Memory corruption in n/a","id":"CVE-2022-30772","kev_date_added":null,"published":"2022-11-15"}],"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-11-20","vendors":["n/a"]},"summary":"Attackers can tamper with SMM communication buffers via out-of-bounds access in InsydeH2O firmware, potentially modifying data or escalating privileges.","url":"https://insights.sbomify.com/CVE-2023-47252/"}