{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-39283 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-39283 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-39283 is a high-severity memory corruption vulnerability in Insyde Insydeh2o, published on 2 Nov 2023. 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-39283 and fix it if it is affected.\n\nWhat it is: CVE-2023-39283 is a high-severity memory corruption vulnerability in Insyde Insydeh2o, published on 2 Nov 2023. 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-39283 in the wild and no public exploit code.\n\nAffected product: Insyde Insydeh2o. 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-39283/ (Markdown: https://insights.sbomify.com/CVE-2023-39283/index.md)","id":"CVE-2023-39283","markdown":"https://insights.sbomify.com/CVE-2023-39283/index.md","name":"CVE-2023-39283","record":{"aliases":["GHSA-hq2f-86fm-7823"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"InsydeH2O BIOS","requires_auth":"low_privilege","summary":"Attackers can exploit SMM memory corruption in InsydeH2O BIOS to escalate privileges by sending arbitrary data to SMRAM.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"insydeh2o","vendor":"insyde"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"An SMM memory corruption vulnerability in the SMM driver (SMRAM write) in CsmInt10HookSmm in Insyde InsydeH2O with kernel 5.0 through 5.5 allows attackers to send arbitrary data to SMM which could lead to privilege escalation.","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-39283","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"insyde:insydeh2o","products":["insyde:insydeh2o"],"type":"memory_corruption","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"Missing authorization in n/a","id":"CVE-2023-39284"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2023-39281"},"products":["n/a"],"published":"2023-11-02","related":[{"cvss_score":9.8,"headline":"Missing authorization in n/a","id":"CVE-2021-41842","kev_date_added":null,"published":"2022-01-05"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2023-22612","kev_date_added":null,"published":"2023-04-11"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2023-22613","kev_date_added":null,"published":"2023-04-11"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2023-22614","kev_date_added":null,"published":"2023-04-11"},{"cvss_score":8.4,"headline":"Memory corruption in n/a","id":"CVE-2023-22615","kev_date_added":null,"published":"2023-04-11"},{"cvss_score":8.2,"headline":"Memory corruption in n/a","id":"CVE-2022-36448","kev_date_added":null,"published":"2022-09-28"},{"cvss_score":8.2,"headline":"Memory corruption in n/a","id":"CVE-2022-35893","kev_date_added":null,"published":"2022-09-23"}],"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":"total"},"state":"PUBLISHED","updated":"2024-09-05","vendors":["n/a"]},"summary":"Attackers can exploit SMM memory corruption in InsydeH2O BIOS to escalate privileges by sending arbitrary data to SMRAM.","url":"https://insights.sbomify.com/CVE-2023-39283/"}