Skip to main content
VulnerabilityPublished

CVE-2024-57629: MonetDB · SQL Injection

Affects MonetDBSource CVE Database V5

0

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 10:12 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. Monitor database logs and network traffic for unusual or malformed SQL queries targeting the tail_type component or exhibiting patterns consistent with SQL injection attempts.
  2. Restrict network access to MonetDB servers by implementing firewall rules and network segmentation to limit exposure to untrusted networks.
  3. Employ Web Application Firewalls (WAFs) or SQL injection detection tools to identify and block malicious SQL statements before they reach the database.
  4. Regularly back up database instances to enable rapid recovery in case of service disruption.
  5. Engage with MonetDB maintainers and community to track the release of official patches or updates addressing this vulnerability and apply them promptly once available.
  6. Consider deploying database query throttling or rate limiting to reduce the risk of DoS from repeated exploit attempts.
  7. If feasible, run MonetDB instances with least privilege principles and isolate critical workloads to minimize impact scope.

Description

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