Cyber Resilience

CVE-2024-0408

Redhat Enterprise Linux 6.0 … 9.0

Published
18 January 2024
Modified
29 August 2025
CVSS Score v3.1 5.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.0032 25th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2024-0408 is a medium-severity Improper Neutralization of Null Byte or NUL Character (CWE-158) vulnerability in Redhat Enterprise Linux. Its CVSS base score is 5.5 (Medium).

Operationally, ranked at the 25th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

EU & UK References

Vulnerability Data

A flaw was found in the X.Org server. The GLX PBuffer code does not call the XACE hook when creating the buffer, leaving it unlabeled. When the client issues another request to access that resource (as with a GetGeometry) or…

more

when it creates another resource that needs to access that buffer, such as a GC, the XSELINUX code will try to use an object that was never labeled and crash because the SID is NULL.

CWE(s)
CWE-158NVD-CWE-Other

Related Threats

CVEs Like This One

CVE-2024-0409Same product: Fedoraproject Fedora
CVE-2023-5367Same product: Fedoraproject Fedora
CVE-2023-0494Same product: Fedoraproject Fedora
CVE-2023-6816Same product: Fedoraproject Fedora
CVE-2025-26595Same product: Redhat Enterprise Linux
CVE-2025-26601Same product: Redhat Enterprise Linux
CVE-2025-26596Same product: Redhat Enterprise Linux
CVE-2025-26599Same product: Redhat Enterprise Linux
CVE-2025-26600Same product: Redhat Enterprise Linux
CVE-2025-26598Same product: Redhat Enterprise Linux

Affected Assets

tigervnc
tigervnc
≤ 1.13.1
x.org
x server
≤ 21.1.11
x.org
xwayland
≤ 23.2.4
fedoraproject
fedora
39
redhat
enterprise linux
6.0, 7.0, 8.0, 9.0
redhat
enterprise linux desktop
7.0
redhat
enterprise linux for ibm z systems
7.0
redhat
enterprise linux for power big endian
7.0
redhat
enterprise linux for power little endian
7.0
redhat
enterprise linux for scientific computing
7.0
+2 more product configuration(s) — see NVD for full list

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)
  • V1.2.10

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 prevent null-byte flaws.

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
detects

Security testing can detect null-byte 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 sanitization that directly prevents null-byte injection.

A.8.26 Application security requirements partial match
prevents

Application security requirements include explicit rules for neutralizing dangerous characters such as NUL.

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

Secure architecture principles reduce the likelihood of unsafe data flows but do not prescribe character neutralization.

A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly require proper neutralization of null bytes and other metacharacters.

References