Skip to main content
VulnerabilityPublished

CVE-2024-57630: MonetDB · SQL Injection

Affects MonetDBSource CVE Database V5

0

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 17:16 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, especially from untrusted or public networks, using firewalls or network segmentation.
  2. Monitor database logs and network traffic for unusual or malformed SQL queries targeting the exps_card component.
  3. Implement Web Application Firewalls (WAFs) or Intrusion Prevention Systems (IPS) with custom rules to detect and block suspicious SQL injection attempts.
  4. Temporarily disable or limit usage of the exps_card component if feasible, pending a patch release.
  5. Stay informed through official MonetDB channels and CVE databases for patches or security advisories addressing this vulnerability.
  6. Plan and test patch deployment procedures to apply updates promptly once available.
  7. Conduct internal security assessments and penetration tests focusing on SQL injection vectors to identify similar weaknesses.
  8. Employ database activity monitoring tools to detect and alert on anomalous query patterns. These measures go beyond generic advice by focusing on component-specific controls, proactive monitoring, and network-level protections tailored to MonetDB environments.

Description

An issue in the exps_card 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…