CVE-2024-57618: MonetDB · Improper Resource Shutdown or Release
Affects MonetDBSource CVE Database V5
Not known to be exploited · CVSS 7.5 High.
Data as of 26 Oct 2026, 13:47 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 46% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 14 Jan 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubmonetdb/MonetDBpkg:github/monetdb/MonetDBOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
- Restrict network access to MonetDB Server instances by implementing strict firewall rules and network segmentation to limit exposure to trusted hosts only.
- Monitor database logs and network traffic for unusual or malformed SQL queries targeting the bind_col_exp component or causing abnormal resource consumption.
- Disable or limit remote access to MonetDB where possible until a security patch is released.
- Regularly check official MonetDB security advisories and update to patched versions promptly once available.
- Employ intrusion detection/prevention systems (IDS/IPS) with custom signatures to detect attempts to exploit this vulnerability.
- Consider deploying rate limiting or query throttling mechanisms to reduce the risk of DoS attacks via crafted SQL statements.
- Conduct internal audits of database usage and access controls to ensure only authorized personnel and applications can interact with MonetDB servers.
- Prepare incident response plans to quickly address potential DoS incidents affecting database availability. These measures go beyond generic advice by focusing on network-level controls, monitoring specific to SQL injection vectors, and proactive detection until official patches are released.
Description
An issue in the bind_col_exp component of MonetDB Server v11.47.11 allows attackers to cause a Denial of Service (DoS) via crafted SQL statements.