{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-34338 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-34338 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-34338 is a high-severity vulnerability in AMI MegaRAC_SPx, published on 5 Jul 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2023-34338 and fix it if it is affected.\n\nWhat it is: CVE-2023-34338 is a high-severity vulnerability in AMI MegaRAC_SPx, published on 5 Jul 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2023-34338 in the wild and no public exploit code.\n\nAffected product: AMI MegaRAC_SPx. 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-34338/ (Markdown: https://insights.sbomify.com/CVE-2023-34338/index.md)","id":"CVE-2023-34338","markdown":"https://insights.sbomify.com/CVE-2023-34338/index.md","name":"CVE-2023-34338","record":{"aliases":["GHSA-mc2f-w8rf-jpvf"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["data_read","data_modify","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"BMC firmware","requires_auth":"none","summary":"An attacker can exploit a hard-coded cryptographic key in AMI MegaRAC SPx BMC firmware to compromise confidentiality, integrity, and availability.","user_interaction":"required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"AMI","cpe":[{"product":"megarac_sp-x","vendor":"ami"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:A/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"},{"id":"CWE-321","name":"Use of Hard-coded Cryptographic Key"}],"description":"AMI SPx contains a vulnerability in the BMC where an Attacker may cause a use of hard-coded cryptographic key by a hard-coded certificate. A successful exploit of this vulnerability may lead to a loss of confidentiality, integrity, and availability.","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":"hard coded cryptographic key","id":"CVE-2023-34338","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"Information disclosure in Ktor","id":"CVE-2023-34339"},"packages":[],"prev":{"headline":"Inadequate Encryption Strength","id":"CVE-2023-34337"},"products":["MegaRAC_SPx"],"published":"2023-07-05","related":[{"cvss_score":10,"headline":"AMI MegaRAC SPx Authentication Bypass by Spoofing","id":"CVE-2024-54085","kev_date_added":"2025-06-25","published":"2025-03-11"},{"cvss_score":9.6,"headline":"Stack-based Buffer Overflow BMC","id":"CVE-2023-3043","kev_date_added":null,"published":"2024-01-09"},{"cvss_score":9.6,"headline":"stack-based buffer overflow","id":"CVE-2023-37293","kev_date_added":null,"published":"2024-01-09"},{"cvss_score":9.1,"headline":"Authentication Bypass via HTTP Header Spoofing","id":"CVE-2023-34329","kev_date_added":null,"published":"2023-07-18"},{"cvss_score":9.1,"headline":"Other in n/a","id":"CVE-2023-28863","kev_date_added":null,"published":"2023-04-18"},{"cvss_score":8.3,"headline":"Heap-based Buffer Overflow","id":"CVE-2023-37294","kev_date_added":null,"published":"2024-01-09"},{"cvss_score":8.3,"headline":"Heap-based Buffer Overflow","id":"CVE-2023-37295","kev_date_added":null,"published":"2024-01-09"}],"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-11-21","vendors":["AMI"]},"summary":"An attacker can exploit a hard-coded cryptographic key in AMI MegaRAC SPx BMC firmware to compromise confidentiality, integrity, and availability.","url":"https://insights.sbomify.com/CVE-2023-34338/"}