Skip to main content
VulnerabilityPublished Updated

CVE-2024-57624: MonetDB · SQL Injection

Affects MonetDBSource CVE Database V5

0

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 12:54 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 48% 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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 Jan 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
GitHubmonetdb/MonetDBpkg:github/monetdb/MonetDBOther threatsAffected
  • =11.49.1
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Immediately restrict network access to MonetDB Server instances, limiting connections to trusted hosts and internal networks only.
  2. Implement firewall rules or network segmentation to prevent unauthorized external access to the database server.
  3. Employ query filtering or input validation proxies where possible to detect and block suspicious or malformed SQL statements targeting the exp_atom component.
  4. Monitor database logs and network traffic for unusual query patterns or spikes in failed requests that may indicate exploitation attempts.
  5. Prepare for rapid deployment of official patches or updates from MonetDB developers once released; subscribe to MonetDB security advisories.
  6. Consider temporary disabling or isolating vulnerable database instances in high-risk environments until a fix is available.
  7. Conduct internal audits of MonetDB usage to identify and prioritize critical systems for protection.
  8. Educate database administrators and security teams about this vulnerability and recommended defensive measures.

Description

An issue in the exp_atom component of MonetDB Server v11.49.1 allows attackers to cause a Denial of Service (DoS) via crafted SQL statements.

References

Community reviews

Loading reviews…