CVE-2024-23615
Published: 26 January 2024
Summary
CVE-2024-23615 is a critical-severity Improper Restriction of Operations within the Bounds of a Memory Buffer (CWE-119) vulnerability in Broadcom Symantec Messaging Gateway. Its CVSS base score is 10.0 (Critical).
Operationally, ranked in the top 8.9% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis
A buffer overflow vulnerability exists in Symantec Messaging Gateway versions 10.5 and earlier, specifically within the libdec2lha.so component. The flaw is tracked as CVE-2024-23615 with associated CWEs 119 and 120, and it received a CVSS 3.1 score of 10.0 reflecting network-accessible attack complexity that is low with no required privileges or user interaction.
An unauthenticated remote attacker can send specially crafted input to trigger the overflow, resulting in arbitrary code execution with root privileges on the messaging gateway.
Technical analysis published by Exodus Intel describes the stack-based overflow in detail and confirms the path to remote root code execution. The EPSS score has remained flat at 0.0630 with no material rise observed after disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-21109
Vulnerability details
A buffer overflow vulnerability exists in Symantec Messaging Gateway versions 10.5 and before. A remote, anonymous attacker can exploit this vulnerability to achieve remote code execution as root.
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
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.
Managed runtimes used by platform-independent applications (e.g., JVM, CLR) enforce memory safety, preventing most buffer overflows that require direct memory manipulation.
Ongoing control assessments and code testing (static/dynamic analysis, fuzzing) surface memory buffer restriction failures, which are then remediated before release.
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.