Skip to main content
VulnerabilityPublished Updated

CVE-2024-57627: MonetDB · SQL Injection

Affects MonetDBSource CVE Database V5

0

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 09:15 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

Until an official patch is released, organizations should implement several specific mitigation strategies: 1) Restrict network access to MonetDB instances by enforcing strict firewall rules and limiting connections to trusted hosts only. 2) Deploy Web Application Firewalls (WAFs) or SQL query filtering mechanisms to detect and block suspicious or malformed SQL statements targeting the gc_col component. 3) Monitor database logs and network traffic for unusual query patterns or repeated failed requests that may indicate exploitation attempts. 4) Consider temporarily disabling or isolating vulnerable MonetDB instances from public or untrusted networks. 5) Implement rate limiting on database query submissions to reduce the risk of automated DoS attacks. 6) Prepare incident response plans to quickly recover from potential outages, including database restarts and failover procedures. 7) Stay informed through official MonetDB and CVE sources for forthcoming patches and apply them promptly once available. These targeted actions go beyond generic advice by focusing on access control, query inspection, and operational readiness specific to MonetDB environments.

Description

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