CVE-2023-5215
Redhat Enterprise Linux 8.0 … 9.0
Raw vector
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-5215 is a medium-severity Improper Handling of Unexpected Data Type (CWE-241) vulnerability in Redhat Enterprise Linux. Its CVSS base score is 5.3 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 48% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-57545
Vulnerability Data
A flaw was found in libnbd. A server can reply with a block size larger than 2^63 (the NBD spec states the size is a 64-bit unsigned value). This issue could lead to an application crash or other unintended behavior…
more
for NBD clients that doesn't treat the return value of the nbd_get_size() function correctly.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
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.
Secure SDLC practices directly require proper input validation and type checking to prevent this weakness.
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.
Security testing can detect type-handling flaws but does not itself implement the preventive control.
Secure development lifecycle includes input validation and type checking that directly mitigates improper handling of unexpected data types.
Application security requirements typically mandate strong input validation and type enforcement to prevent malformed data processing.
Secure system architecture principles encourage robust input handling but do not specifically address data-type validation.
Secure coding standards explicitly require type checking and input sanitization, directly addressing improper handling of unexpected data types.