AMI MegaRAC SPx12 contains a vulnerability in BMC where a User may cause an authentication bypass by spoofing the HTTP header. A successful exploit of this vulnerability may lead to loss of confidentiality, integrity, and availability.
Severity
CVSS 3.1
8.0 high
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
1.2%(unchanged from 1.2% a week ago; 1.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 69th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2024-10-25. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-290Authentication Bypass by Spoofing CWE-306Missing Authentication for Critical Functionality
Show the promptExplain CVE-2023-34329 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2023-34329?via=ask-ai-copy and https://cve.bz/cve/CVE-2023-34329?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2023-34329 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.
Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.
Emerging Threats Open ET WEB_SERVER MegaRAC Redfish Authentication Bypass via HTTP Header Spoofing (CVE-2023-34329) sid 2065041
Attack patterns (CAPEC)
CAPEC-12 Choosing Message Identifier Likelihood: High · Severity: High
CAPEC-36 Using Unpublished Interfaces or Functionality Likelihood: Medium · Severity: High
CAPEC-62 Cross Site Request Forgery Likelihood: High · Severity: Very High
CAPEC-166 Force the System to Reset Values Severity: Medium