{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-52712 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-52712 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-52712 is a high-severity vulnerability in Huawei CurieM-WFG9B, published on 28 May 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-52712 and fix it if it is affected.\n\nWhat it is: CVE-2023-52712 is a high-severity vulnerability in Huawei CurieM-WFG9B, published on 28 May 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-52712 in the wild and no public exploit code.\n\nAffected product: Huawei CurieM-WFG9B. 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-52712/ (Markdown: https://insights.sbomify.com/CVE-2023-52712/index.md)","id":"CVE-2023-52712","markdown":"https://insights.sbomify.com/CVE-2023-52712/index.md","name":"CVE-2023-52712","record":{"aliases":[],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Huawei firmware","requires_auth":"low_privilege","summary":"Exposed SMI handler allows bypassing SPI flash protections and corrupting SMM memory, potentially leading to code execution in System Management Mode.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"huawei","cpe":[{"product":"curiem-wfg9b_firmware","vendor":"huawei"}],"cvss":{"score":7.8,"severity":"high","source":"cna","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-284","name":"Improper Access Control"}],"description":"Various Issues Due To Exposed SMI Handler in AmdPspP2CmboxV2. The first issue can be leveraged to bypass the protections that have been put in place by previous UEFI phases to prevent direct access to the SPI flash. The second issue can be used to both leak and corrupt SMM memory, thus potentially leading code execution in SMM","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 CurieM-WFG9B","id":"CVE-2023-52712","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"Missing authorization in EMUI","id":"CVE-2023-52713"},"packages":[],"prev":{"headline":"Privilege escalation in CurieM-WFG9B","id":"CVE-2023-52711"},"products":["CurieM-WFG9B"],"published":"2024-05-28","related":[{"cvss_score":7.8,"headline":"Memory corruption in CurieM-WFG9B","id":"CVE-2023-52547","kev_date_added":null,"published":"2024-05-28"},{"cvss_score":7.8,"headline":"Memory corruption in CurieM-WFG9B","id":"CVE-2023-52548","kev_date_added":null,"published":"2024-05-28"},{"cvss_score":7.8,"headline":"Memory corruption in CurieM-WFG9B","id":"CVE-2023-52710","kev_date_added":null,"published":"2024-05-28"},{"cvss_score":7.8,"headline":"Privilege escalation in CurieM-WFG9B","id":"CVE-2023-52711","kev_date_added":null,"published":"2024-05-28"}],"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-08-02","vendors":["Huawei"]},"summary":"Exposed SMI handler allows bypassing SPI flash protections and corrupting SMM memory, potentially leading to code execution in System Management Mode.","url":"https://insights.sbomify.com/CVE-2023-52712/"}