CVE-2023-52971

MariaDB Server 10.10 through 10.11.* and 11.0 through 11.4.* crashes in JOIN::fix_all_splittings_in_plan.

Published: 2025-03-08 Last update: 2026-04-15 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2023-52971 is rated Low Risk (25.4/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.05%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2023-52971

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2025-12-23 0.03% 0.05% +0.02%
2 2025-11-21 0.16% 0.03% -0.13%
3 2025-11-18 — 0.16% —

Full EPSS history (8 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2023-52971

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
4.9 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:H)
They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.2 3.6 [email protected]

Weakness enumeration for CVE-2023-52971

OS Trackers for CVE-2023-52971

vendor priority summary link
debian unimportant CVE-2023-52971 unimportant priority: Debian including 2 source packages (mariadb, mariadb-10.5), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2023-52971
redhat medium — https://access.redhat.com/security/cve/CVE-2023-52971
suse medium CVE-2023-52971 severity moderate: SUSE including 29 source package names (10.11.14-63.28:mariadb-client-10.11.14-150600.4.14.1, 10.11.14-63.28:mariadb-errormessages-10.11.14-150600.4.14.1, …), 148 product×package rows across 28 product lines (Container suse/mariadb, Container suse/mariadb-client, … (28 product lines)): Known Not Affected 125, Fixed 23. https://www.suse.com/security/cve/CVE-2023-52971/
ubuntu medium CVE-2023-52971 medium priority: Ubuntu including 1 source packages (mariadb), 7 status rows across 7 suites (focal, jammy, noble, oracular, plucky, questing, upstream): released 3, DNE 2, ignored 1, not-affected 1. https://ubuntu.com/security/CVE-2023-52971

Affected software / configurations for CVE-2023-52971

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2023-52971

cvelogic Threat Intelligence