CVE-2024-57617

7.5 HIGH

📋 TL;DR

This vulnerability in MonetDB Server's dameraulevenshtein component allows attackers to execute crafted SQL statements that cause a Denial of Service (DoS) by crashing or hanging the database server. It affects MonetDB Server version 11.49.1 and potentially earlier versions. Organizations running vulnerable MonetDB instances are at risk of service disruption.

💻 Affected Systems

Products:
  • MonetDB Server
Versions: v11.49.1 and potentially earlier versions
Operating Systems: All platforms running MonetDB
Default Config Vulnerable: ⚠️ Yes
Notes: Any MonetDB installation using the dameraulevenshtein component with default configuration is vulnerable.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database service outage requiring server restart, potentially causing extended downtime and data unavailability.

🟠

Likely Case

Temporary service disruption affecting database operations until the server is restarted.

🟢

If Mitigated

Minimal impact with proper input validation and monitoring in place to detect and block malicious queries.

🌐 Internet-Facing: HIGH - Internet-facing MonetDB instances are directly exposed to crafted SQL injection attacks.
🏢 Internal Only: MEDIUM - Internal instances are still vulnerable to insider threats or compromised internal systems.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: MEDIUM

Requires ability to execute SQL statements against the database, typically through application access or database credentials.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Check GitHub issue for latest patched version

Vendor Advisory: https://github.com/MonetDB/MonetDB/issues/7432

Restart Required: No

Instructions:

1. Check the GitHub issue for the latest patched version. 2. Upgrade MonetDB Server to the patched version. 3. Test the upgrade in a non-production environment first.

🔧 Temporary Workarounds

Disable dameraulevenshtein component

all

Temporarily disable or restrict access to the vulnerable dameraulevenshtein functionality

-- Configuration depends on MonetDB setup and usage patterns

Implement SQL input validation

all

Add application-level validation to filter or sanitize SQL queries before execution

-- Implementation specific to application framework

🧯 If You Can't Patch

  • Implement network segmentation to restrict database access to trusted sources only
  • Deploy web application firewall (WAF) with SQL injection protection rules
  • Monitor database logs for unusual SQL patterns and implement rate limiting

🔍 How to Verify

Check if Vulnerable:

Check MonetDB version: if running v11.49.1 or earlier, assume vulnerable. Test with controlled SQL queries using dameraulevenshtein functions.

Check Version:

SELECT monetdb_version();

Verify Fix Applied:

After patching, verify version is updated and test that previously crashing SQL queries no longer cause DoS.

📡 Detection & Monitoring

Log Indicators:

  • Database crash logs
  • Unusual dameraulevenshtein function calls
  • SQL query patterns causing high resource usage

Network Indicators:

  • Sudden drop in database connectivity
  • Increased error responses from database layer

SIEM Query:

source="monetdb.log" AND ("crash" OR "segfault" OR "dameraulevenshtein")

🔗 References

📤 Share & Export