CVE-2023-3824
Memory Safety in Php 8.0.0 – 8.0.30
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:LSummary
CVE-2023-3824 is a critical-severity Improper Restriction of Operations within the Bounds of a Memory Buffer (CWE-119) vulnerability in Php Php. Its CVSS base score is 9.4 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Process Injection (T1055); ranked in the top 3% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2023-3824 is a stack buffer overflow vulnerability in PHP versions 8.0.* before 8.0.30, 8.1.* before 8.1.22, and 8.2.* before 8.2.8. It occurs when loading a phar file and reading PHAR directory entries due to insufficient length checking, which can result in memory corruption or remote code execution. The flaw is tracked under CWE-119 and carries a CVSS 3.1 score of 9.4 reflecting network-accessible attack vectors with high impact on confidentiality and integrity.
An unauthenticated attacker can trigger the issue by supplying a malicious phar archive that a vulnerable PHP application loads, enabling memory corruption or arbitrary code execution on the affected system without requiring user interaction.
Advisories from the PHP project, Debian, Fedora, and NetApp recommend upgrading to the fixed releases 8.0.30, 8.1.22, or 8.2.8. The associated EPSS score has remained in the 0.32–0.35 range since disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-44452
Vulnerability Data
In PHP version 8.0.* before 8.0.30, 8.1.* before 8.1.22, and 8.2.* before 8.2.8, when loading phar file, while reading PHAR directory entries, insufficient length checking may lead to a stack buffer overflow, leading potentially to memory corruption or RCE.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V17.3.2
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Ongoing control assessments and code testing (static/dynamic analysis, fuzzing) surface memory buffer restriction failures, which are then remediated before release.
Managed runtimes used by platform-independent applications (e.g., JVM, CLR) enforce memory safety, preventing most buffer overflows that require direct memory manipulation.
Memory protections (e.g., W^X, ASLR) make exploitation of buffer-boundary violations far harder to turn into code execution.
Detects exploitation attempts that produce memory corruption, crashes, or anomalous behavior.
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 (bounds checking, safe APIs, reviews) directly prevent this class of flaw.
Vulnerability scanning and code analysis directly surface buffer-boundary flaws.
Receiving and triaging vulnerability disclosures commonly includes buffer-related reports.
Developer training on secure coding reduces introduction of memory-buffer errors.
Patching replaces vulnerable code containing buffer-boundary defects.
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 in development catches out-of-bounds accesses before release, covering most instances of the weakness.
Secure development lifecycle mandates memory-safety practices that directly prevent buffer-boundary violations.
Application security requirements can specify memory-safety rules, but do not prescribe implementation details.
Secure architecture and engineering principles include memory-safe design patterns that mitigate buffer overflows.
Secure coding standards explicitly forbid unsafe buffer operations, directly eliminating CWE-119.