{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-31100 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-31100 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-31100 is a high-severity missing authorization vulnerability in Phoenix SecureCore™ Technology™ 4, published on 14 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-31100 and fix it if it is affected.\n\nWhat it is: CVE-2023-31100 is a high-severity missing authorization vulnerability in Phoenix SecureCore™ Technology™ 4, published on 14 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-31100 in the wild and no public exploit code.\n\nAffected product: Phoenix SecureCore™ Technology™ 4. 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-31100/ (Markdown: https://insights.sbomify.com/CVE-2023-31100/index.md)","id":"CVE-2023-31100","markdown":"https://insights.sbomify.com/CVE-2023-31100/index.md","name":"CVE-2023-31100","record":{"aliases":["GHSA-h3cr-gxpm-fxxc"],"analysis":{"component_type":"hardware_firmware","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Phoenix SecureCore firmware","requires_auth":"low_privilege","summary":"Attackers can modify SPI flash via improper access control in the SMI handler, potentially leading to code execution or privilege escalation.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Phoenix","cpe":[{"product":"securecore_technology","vendor":"phoenixtech"}],"cvss":{"score":8.4,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-284","name":"Improper Access Control"}],"description":"Improper Access Control in SMI handler vulnerability in Phoenix SecureCore™ Technology™ 4 allows SPI flash modification.\nThis issue affects SecureCore™ Technology™ 4:\n\n  *  from 4.3.0.0 before 4.3.0.203\n  *  \n\nfrom \n\n4.3.1.0 before 4.3.1.163\n  *  \n\nfrom \n\n4.4.0.0 before 4.4.0.217\n  *  \n\nfrom \n\n4.5.0.0 before 4.5.0.138","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":"Missing authorization in SecureCore™ Technology™ 4","id":"CVE-2023-31100","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"Apache InLong: Users who joined later can see the data of deleted users","id":"CVE-2023-31101"},"packages":[],"prev":{"headline":"Code injection in n/a","id":"CVE-2023-31099"},"products":["SecureCore™ Technology™ 4"],"published":"2023-11-14","related":[{"cvss_score":7.8,"headline":"Other in SecureCore™ Technology™ 4","id":"CVE-2023-5058","kev_date_added":null,"published":"2023-12-07"},{"cvss_score":7.5,"headline":"Potential buffer overflow when handling UEFI variables","id":"CVE-2024-0762","kev_date_added":null,"published":"2024-05-14"},{"cvss_score":7.5,"headline":"Potential buffer overflow when handling UEFI variables","id":"CVE-2024-1598","kev_date_added":null,"published":"2024-05-14"},{"cvss_score":4.6,"headline":"Unsafe Handling of Phoenix UEFI Variables","id":"CVE-2024-29979","kev_date_added":null,"published":"2025-01-14"},{"cvss_score":4.6,"headline":"Unsafe Handling of IHV UEFI Variables","id":"CVE-2024-29980","kev_date_added":null,"published":"2025-01-14"},{"cvss_score":3.3,"headline":"Other in SecureCore Technology 4","id":"CVE-2024-12533","kev_date_added":null,"published":"2025-05-13"}],"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":"2025-07-28","vendors":["Phoenix"]},"summary":"Attackers can modify SPI flash via improper access control in the SMI handler, potentially leading to code execution or privilege escalation.","url":"https://insights.sbomify.com/CVE-2023-31100/"}