LiveActive security incident?Get immediate response
CVE Record

CVE-2023-34472: AMI SPx contains a vulnerability in the BMC where an Attacker may cause an improper neutralization of CRLF...

AMI SPx contains a vulnerability in the BMC where an Attacker may cause an improper neutralization of CRLF sequences in HTTP Headers. A successful exploit of this vulnerability may lead to a loss of integrity.

MediumCVSS 5.7Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-34472 affects AMI MegaRAC SPx BMC firmware versions 12.0 and 13.0. An authenticated attacker on an adjacent network may be able to manipulate HTTP headers through CRLF handling, creating an integrity risk. The source bundle does not show public exploitation or a specific fix.

Executive priority

Treat as a management-plane integrity issue with moderate urgency. It is not presented as actively exploited, but BMC exposure can carry outsized operational risk because these systems manage server hardware beneath the operating system.

Technical view

The issue is improper neutralization of CRLF sequences in HTTP headers in AMI SPx BMC software, mapped to CWE-113 and CWE-93. CVSS 3.1 is 5.7: adjacent network, low privileges, no user interaction, high integrity impact, no confidentiality or availability impact.

Likely exposure

Exposure is most relevant where AMI MegaRAC SPx 12.0 or 13.0 BMC interfaces are reachable from adjacent or poorly segmented management networks and where low-privilege BMC credentials exist.

Exploitation context

The CVE is not listed as KEV, and the provided sources do not cite active exploitation. Exploitation requires adjacent network access and low privileges, limiting broad internet-driven risk but still mattering for management-plane compromise paths.

Researcher notes

Evidence is limited to the CVE record fields and AMI advisory reference in the source bundle. Do not assume affected OEM platforms, exploit availability, or patch identifiers without reviewing the linked advisory and relevant OEM firmware guidance.

Mitigation direction

  • Inventory systems using AMI MegaRAC SPx 12.0 or 13.0.
  • Check AMI and server OEM advisories for approved firmware updates or mitigations.
  • Restrict BMC access to trusted management networks only.
  • Review and minimize low-privilege BMC accounts.
  • Prioritize remediation for shared, hosted, or weakly segmented infrastructure.

Validation and detection

  • Confirm BMC firmware product and version from asset records or management tools.
  • Verify BMC interfaces are not reachable outside approved management segments.
  • Review BMC account lists for unnecessary low-privilege users.
  • Check vendor or OEM advisory status for each affected platform.
  • Monitor BMC logs for unusual authenticated web management activity.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-113: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cwe · low confidence lookup

CWE-93: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-34472 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.7 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.7CVSS 3.1MediumCVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N2.13.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.7Medium
CVSS 3.1 vector shape for CVE-2023-34472Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
AMIMegaRAC_SPx12.0, 13.0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-113 · source CWE mapping

Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting')

Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

CWE-93 · source CWE mapping

Improper Neutralization of CRLF Sequences ('CRLF Injection')

Improper Neutralization of CRLF Sequences ('CRLF Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.