Cyber Resilience

CVE-2023-2602

Redhat Enterprise Linux 6.0 … 9.0

Public PoC
Published
06 June 2023
Modified
21 November 2024
CVSS Score v3.1 3.3
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:L
EPSS Score 0.0035 28th percentile
Risk Priority 15 floored blend · peak EPSS

Summary

CVE-2023-2602 is a low-severity Missing Release of Memory after Effective Lifetime (CWE-401) vulnerability in Redhat Enterprise Linux. Its CVSS base score is 3.3 (Low).

Operationally, ranked at the 28th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

EU & UK References

Vulnerability Data

A vulnerability was found in the pthread_create() function in libcap. This issue may allow a malicious actor to use cause __real_pthread_create() to return an error, which can exhaust the process memory.

CWE(s)

Related Threats

CVEs Like This One

CVE-2023-2603Same product: Debian Debian Linux
CVE-2023-2700Same product: Fedoraproject Fedora
CVE-2023-33460Same product: Debian Debian Linux
CVE-2023-34966Same product: Debian Debian Linux
CVE-2023-1667Same product: Debian Debian Linux
CVE-2023-38559Same product: Debian Debian Linux
CVE-2023-2156Same product: Debian Debian Linux
CVE-2024-1151Same product: Debian Debian Linux
CVE-2023-44488Same product: Debian Debian Linux
CVE-2023-34967Same product: Debian Debian Linux

Affected Assets

libcap project
libcap
2.66
redhat
enterprise linux
6.0, 7.0, 8.0, 9.0
debian
debian linux
10.0, 11.0, 12.0
fedoraproject
fedora
37, 38

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.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly enforce proper memory allocation/deallocation via coding standards, reviews, and tooling.

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.

detects

Security testing in development can detect unreleased memory, providing partial coverage of the weakness.

prevents

Secure development life cycle mandates memory-management practices that reduce missing-release defects.

prevents

Application security requirements can specify explicit memory-release rules, partially mitigating the weakness.

prevents

Secure system architecture and engineering principles include resource-management guidelines that address memory leaks.

prevents

Secure coding standards directly require proper allocation/deallocation, covering most of this weakness.

detects

Capacity management may detect memory exhaustion symptoms but does not prevent the coding flaw.

References