CVE-2024-57632: MonetDB · SQL Injection
Affects MonetDBSource CVE Database V5
Not known to be exploited · CVSS 7.5 High.
Data as of 26 Oct 2026, 09:15 UTC
- EPSS
- 0.8% chance of exploitation in 30 days – higher than 56% 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
Until an official patch is released, organizations should implement several specific mitigations: 1) Restrict network access to MonetDB servers by enforcing strict firewall rules and limiting connections to trusted hosts only. 2) Employ database query filtering or input validation proxies to detect and block suspicious or malformed SQL statements targeting the is_column_unique component. 3) Monitor database logs and network traffic for unusual query patterns indicative of exploitation attempts. 4) Implement rate limiting on SQL query submissions to reduce the risk of automated DoS attacks. 5) Consider deploying MonetDB instances behind VPNs or within isolated network segments to minimize exposure. 6) Prepare incident response plans for rapid recovery from potential DoS events, including database restarts and failover procedures. 7) Stay updated with MonetDB vendor announcements and apply patches immediately once available. 8) Conduct internal security assessments and penetration tests focusing on SQL injection vectors to identify other potential weaknesses.
Description
An issue in the is_column_unique component of MonetDB Server v11.49.1 allows attackers to cause a Denial of Service (DoS) via crafted SQL statements.