Security Resilience

CVE-2023-40547

Memory Safety in Redhat Shim ≤ 15.8

Published
25 January 2024
Modified
26 June 2026
Patch / advisory
CVSS Score v3.1 8.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
EPSS Score 0.054 93th percentile
Risk Priority 66 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2023-40547 is a high-severity Out-of-bounds Write (CWE-787) vulnerability in Redhat Shim. Its CVSS base score is 8.3 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 7% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-4 (Information Flow Enforcement) and IA-3 (Device Identification and Authentication) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

A remote code execution vulnerability was found in Shim. The Shim boot support trusts attacker-controlled values when parsing an HTTP response. This flaw allows an attacker to craft a specific malicious HTTP request, leading to a completely controlled out-of-bounds write…

more

primitive and complete system compromise. This flaw is only exploitable during the early boot phase, an attacker needs to perform a Man-in-the-Middle or compromise the boot server to be able to exploit this vulnerability successfully.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

MITRE ATT&CK v20.0

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1189 Drive-by Compromise Initial Access
Adversaries may gain access to a system through a user visiting a website over the normal course of browsing.
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.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
T1499.004 Application or System Exploitation Impact
Adversaries may exploit software vulnerabilities that can cause an application or system to crash and deny availability to users.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-0646Same vendor: Redhat
CVE-2023-6228Same vendor: Redhat
CVE-2023-52355Same vendor: Redhat
CVE-2023-3812Same vendor: Redhat
CVE-2023-3138Same vendor: Redhat
CVE-2023-40548Same product: Redhat Shim
CVE-2023-3164Same vendor: Redhat
CVE-2024-8443Same vendor: Redhat
CVE-2023-4692Same vendor: Redhat
CVE-2023-42753Same vendor: Redhat

Affected Assets

redhat
shim
≤ 15.8
redhat
enterprise linux
7.0, 8.0, 9.0

Mitigating Controls

Mitigating Controls (NIST 800-53 r5)

Our mappings, made for this CVE.

Information flow enforcement directly requires validating the source of data before allowing transmission or receipt.

Device identification and authentication mandates verifying the source before establishing connections.

Developer testing and evaluation (including fuzzing and bounds checks) finds out-of-bounds write flaws before deployment.

Session authenticity mechanisms require validation that communications originate from the expected party.

Requiring documented secure-development standards and tools can mandate bounds-checked coding practices that avoid the weakness.

Boundary protection at interfaces enforces checks on the origin of incoming communications.

Mitigating Controls (NIST CSF 2.0)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.

PR.PS-06 mostly match
blocks

Secure-development practices (static analysis, bounds checking, code review) are the primary means of preventing out-of-bounds writes.

ID.RA-01 partial match
blocks

Vulnerability scanning and recording can discover out-of-bounds write flaws so they can be remediated.

PR.PS-02 partial match
blocks

Patching or replacing vulnerable software directly eliminates known instances of this coding weakness.

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

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.

finds

Security testing in development and acceptance can detect and prevent out-of-bounds write defects.

prevents

Training developers in secure coding practices (bounds checking, safe memory handling) reduces some out-of-bounds write instances, but the defect requires deep technical knowledge and even trained developers make these mistakes, so only a minority of instances are prevented.

prevents

Secure coding directly addresses out-of-bounds writes through language choice and coding standards.

prevents

A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary implementation-phase memory-safety defects in delivered code the way those practices do; the clause has a declared ceiling of `partial` on this verb, and the same reasoning that graded A.8.30 -> CWE-134 `partial` applies here.

finds

A.8.8's reach is DISCLOSURE — it finds vulnerabilities via published advisories and component inventory, which surfaces out-of-bounds writes in third-party components where they commonly appear as CVEs, but most CWE-787 instances are in first-party code that no advisory names, leaving a nameable remainder outside its view.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-346, a class-level weakness, and none of its children carries one either.

References