FERRAMENTAS LINUX: Critical MariaDB Vulnerabilities in Mageia 9: Security Risks, Fixes, and Best Practices

quinta-feira, 12 de junho de 2025

Critical MariaDB Vulnerabilities in Mageia 9: Security Risks, Fixes, and Best Practices

Mageia 9 users face critical MariaDB vulnerabilities (CVE-2023-52969, CVE-2023-52970, CVE-2023-52971) leading to crashes and denial-of-service risks. Learn how updated MariaDB 11.4.7 patches these flaws and secure your database server now.

Why Mageia 9 Users Must Act Now

MariaDB, a widely used open-source database system, has been found vulnerable to multiple high-severity crashes and denial-of-service (DoS) risks in Mageia 9. These vulnerabilities affect versions 10.4 through 11.4, exposing systems to instability and potential exploitation.

Key Risks:

CVE-2023-52969: Crashes due to empty backtrace logs in make_aggr_tables_info and optimize_stage2.
CVE-2023-52970: Crashes in Item_direct_view_ref::derived_field_transformer_for_where.
CVE-2023-52971: Crashes in JOIN::fix_all_splittings_in_plan.

If you're running an unpatched MariaDB server, your system could be at risk.

Affected MariaDB Versions and Security Implications

Vulnerability Breakdown

CVE ID	Affected Versions	Risk Impact
CVE-2023-52969	MariaDB 10.4–11.0	Server crash (DoS)
CVE-2023-52970	MariaDB 10.4–11.4	Query processing crash
CVE-2023-52971	MariaDB 10.10–11.4	JOIN operation failure

These flaws can lead to:

✔ Unexpected database crashes

✔ Service disruptions

✔ Potential exploitation by attackers

Steps to Secure Your System:

Update Immediately:
bash
Copy
Download
```
sudo urpmi --auto-update --auto mariadb
```
Verify Installation:
bash
Copy
Download
```
mariadb --version
```
Restart Services:
bash
Copy
Download
```
sudo systemctl restart mariadb
```

How to Fix Mageia 9 MariaDB Vulnerabilities

Official Patch: MGASA-2025-0186

Mageia has released an updated MariaDB package (11.4.7-1.mga9) to address these security flaws.

Why This Matters:

Prevents unauthorized crashes
Ensures database stability
Mitigates potential exploits

Additional Security Best Practices for MariaDB

1. Enable Logging & Monitoring

Configure error logging to detect crashes early.
Use fail2ban to block brute-force attacks.

2. Apply Principle of Least Privilege

Restrict database user permissions.
Avoid running MariaDB as root.

3. Regular Backups

Schedule automated mysqldump backups.
Store backups offsite for disaster recovery.

Frequently Asked Questions (FAQ)

Q: Are MySQL servers also affected?

A: Yes, Oracle MySQL (8.0.0–8.0.41, 8.4.0–8.4.4, 9.0.0–9.2.0) has a separate vulnerability (CVE-2025-30693) leading to hang/crash risks.

Q: How critical are these flaws?

A: These are moderate-to-high severity due to potential DoS and stability issues.

Q: Can attackers exploit these remotely?

A: Some vulnerabilities require network access, making them exploitable in exposed environments.

Conclusion: Secure Your Database Now

Mageia 9 users must update MariaDB immediately to prevent crashes and security risks. Follow best practices like logging, least privilege, and backups to maintain a robust database environment.

🔗 Further Reading: