Cyber Resilience

CVE-2023-34472

Ami Megarac Sp-X 12 … 13

Published
05 July 2023
Modified
21 November 2024
Patch / advisory
View advisory
CVSS Score v3.1 5.7
Click a component to see what it means
Raw vectorCVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
EPSS Score 0.0048 39th percentile
Risk Priority 45 floored blend · peak EPSS

Summary

CVE-2023-34472 is a medium-severity CRLF Injection (CWE-93) vulnerability in Ami Megarac Sp-X. Its CVSS base score is 5.7 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Content Injection (T1659); ranked at the 39th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

A05:2025 Injection

EU & UK References

Vulnerability Data

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.

CWE(s)
CWE-93CWE-113NVD-CWE-Other

Related Threats

MITRE ATT&CK Enterprise Techniques

T1659 Content Injection Initial Access
Adversaries may gain access and continuously communicate with victims by injecting malicious content into systems through online network traffic.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-34342Same product: Ami Megarac Sp-X
CVE-2023-34345Same product: Ami Megarac Sp-X
CVE-2023-34334Same product: Ami Megarac Sp-X
CVE-2023-34336Same product: Ami Megarac Sp-X
CVE-2023-34343Same product: Ami Megarac Sp-X
CVE-2023-34341Same product: Ami Megarac Sp-X
CVE-2023-34333Same product: Ami Megarac Sp-X
CVE-2023-34332Same product: Ami Megarac Sp-X
CVE-2023-37296Same product: Ami Megarac Sp-X
CVE-2023-37294Same product: Ami Megarac Sp-X

Affected Assets

ami
megarac sp-x
12, 13

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V3.4.2
  • V4.1.3
  • V1.3.6
  • V4.2.3

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input neutralization and validation to block CRLF injection.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect CRLF flaws but does not itself implement the neutralization.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle mandates input validation and output encoding that directly prevents CRLF injection.

A.8.26 Application security requirements partial match
prevents

Application security requirements include rules for neutralizing special characters such as CRLF in inputs.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles encourage safe handling of untrusted data but do not prescribe specific CRLF controls.

A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly require neutralization of CRLF sequences, fully addressing this weakness.

A.8.15 Logging none match
none

Logging of HTTP traffic can record header-splitting attempts, aiding detection and forensics.

References