CVE-2023-52971

4.9 MEDIUM

📋 TL;DR

A denial-of-service vulnerability in MariaDB Server causes crashes when processing certain JOIN queries. This affects MariaDB Server versions 10.10 through 10.11.* and 11.0 through 11.4.*, potentially disrupting database availability for applications using these versions.

💻 Affected Systems

Products:
  • MariaDB Server
Versions: 10.10 through 10.11.* and 11.0 through 11.4.*
Operating Systems: All platforms running affected MariaDB versions
Default Config Vulnerable: ⚠️ Yes
Notes: All configurations using the affected versions are vulnerable when processing JOIN queries that trigger the bug.

⚠️ Manual Verification Required

This CVE does not have specific version information in our database, so automatic vulnerability detection cannot determine if your system is affected.

Why? The CVE database entry doesn't specify which versions are vulnerable (no version ranges provided by the vendor/NVD).

🔒 Custom verification scripts are available for registered users. Sign up free to download automated test scripts.

Recommended Actions:
  1. Review the CVE details at NVD
  2. Check vendor security advisories for your specific version
  3. Test if the vulnerability is exploitable in your environment
  4. Consider updating to the latest version as a precaution

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database service disruption leading to application downtime and data unavailability until manual restart.

🟠

Likely Case

Intermittent database crashes requiring administrator intervention to restart services, causing temporary application outages.

🟢

If Mitigated

Limited impact with proper monitoring and automated restart mechanisms in place.

🌐 Internet-Facing: MEDIUM - Internet-facing databases could be targeted with crafted queries to cause service disruption.
🏢 Internal Only: LOW - Internal databases are less likely to be targeted but could still be affected by legitimate queries triggering the bug.

🎯 Exploit Status

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

Exploitation requires ability to execute SQL queries against the database, typically requiring database user credentials. The specific JOIN query patterns needed to trigger the crash are not publicly documented.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: MariaDB 10.11.5, 11.0.3, and later versions

Vendor Advisory: https://jira.mariadb.org/browse/MDEV-32084

Restart Required: Yes

Instructions:

1. Check current MariaDB version. 2. Backup databases and configuration. 3. Upgrade to MariaDB 10.11.5 or 11.0.3 or later. 4. Restart MariaDB service. 5. Verify upgrade completed successfully.

🔧 Temporary Workarounds

Query Filtering

all

Implement application-level filtering or database proxy to block complex JOIN queries that might trigger the crash.

Connection Limiting

all

Restrict database connections to trusted applications only and implement rate limiting.

🧯 If You Can't Patch

  • Implement strict database user permissions to limit who can execute complex JOIN queries.
  • Deploy database monitoring with automated alerting for crash events and implement automated restart procedures.

🔍 How to Verify

Check if Vulnerable:

Check MariaDB version: If version is between 10.10.0-10.11.4 or 11.0.0-11.0.2, the system is vulnerable.

Check Version:

mysql --version OR SELECT VERSION();

Verify Fix Applied:

After patching, verify version is 10.11.5+ or 11.0.3+ and test database functionality with JOIN queries.

📡 Detection & Monitoring

Log Indicators:

  • MariaDB crash logs
  • Unexpected service termination in system logs
  • Error messages referencing JOIN::fix_all_splittings_in_plan

Network Indicators:

  • Sudden drop in database connections
  • Application errors indicating database unavailability

SIEM Query:

source="mariadb.log" AND ("crash" OR "segmentation fault" OR "JOIN::fix_all_splittings_in_plan")

🔗 References

📤 Share & Export