CVE-2024-57623
Monetdb 11.49.1
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HSummary
CVE-2024-57623 is a high-severity Improper Resource Shutdown or Release (CWE-404) vulnerability in Monetdb Monetdb. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 49% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.
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-2024-57623 affects the HEAP_malloc component in MonetDB Server version 11.49.1. The vulnerability enables attackers to trigger a Denial of Service (DoS) condition by sending crafted SQL statements. It is associated with CWE-404 (Improper Resource Shutdown or Release) and carries a CVSS v3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), indicating high severity primarily due to availability impact.
The attack requires only network access with low complexity and no privileges, authentication, or user interaction. Remote, unauthenticated attackers can exploit it by crafting malicious SQL statements that cause resource exhaustion or improper memory handling in the HEAP_malloc function, leading to service disruption without compromising confidentiality or integrity.
Mitigation details are available in the referenced GitHub issue at https://github.com/MonetDB/MonetDB/issues/7415, which documents the vulnerability in MonetDB's repository.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-53655
Vulnerability Data
An issue in the HEAP_malloc component of MonetDB Server v11.49.1 allows attackers to cause a Denial of Service (DoS) via crafted SQL statements.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation can discover missing or incorrect resource releases after code is written.
Engineering principles can require explicit resource acquisition/release patterns that stop improper shutdown from being introduced.
Priority-based resource allocation limits the blast radius when released resources are not returned to the pool.
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 include coding standards for correct resource allocation and release.
Runtime monitoring can detect resource exhaustion caused by improper shutdown or release.
Lifecycle management of assets can encompass proper resource release at end-of-life or shutdown.
Capacity management helps surface leaks from unreleased resources but does not prevent the coding flaw.
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.
Including restart, recovery and media-handling instructions reduces the likelihood that resources or sensitive data will be left in an exposed or improperly released state after a failure.