CVE-2023-52969
First published: Sat Mar 08 2025(Updated: )
MariaDB Server 10.4 through 10.5.*, 10.6 through 10.6.*, 10.7 through 10.11.*, and 11.0 through 11.0.* can sometimes crash with an empty backtrace log. This may be related to make_aggr_tables_info and optimize_stage2.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| MariaDB | >=10.4<=10.5>=10.6<=10.6>=10.7<=10.11>=11.0<=11.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2023-52969?
CVE-2023-52969 is classified as a severity issue due to the potential for crashes in MariaDB Server.
How do I fix CVE-2023-52969?
To fix CVE-2023-52969, upgrade your MariaDB Server to a version above 11.0.* that is not affected by this vulnerability.
Which versions of MariaDB Server are affected by CVE-2023-52969?
CVE-2023-52969 affects MariaDB Server versions 10.4 to 10.5.*, 10.6.*, 10.7 to 10.11.*, and 11.0.*.
What kind of issue does CVE-2023-52969 cause?
CVE-2023-52969 can cause the MariaDB Server to crash without producing a backtrace log.
Is there a workaround for CVE-2023-52969?
Currently, there are no known workarounds for CVE-2023-52969 other than updating to a patched version.
- collector/mitre-cve
- source/MITRE
- agent/weakness
- agent/references
- agent/description
- agent/first-publish-date
- agent/type
- agent/guess-ai
- agent/software-canonical-lookup
- agent/softwarecombine
- collector/nvd-api
- source/NVD
- agent/source
- agent/author
- agent/last-modified-date
- agent/severity
- agent/tags
- agent/event
- vendor/mariadb
- canonical/mariadb