CVE-2023-52968

MariaDB Server 10.4 before 10.4.33, 10.5 before 10.5.24, 10.6 before 10.6.17, 10.7 through 10.11 before 10.11.7, 11.0 before 11.0.5, and 11.1 before 11.1.4 calls fix_fields_if_needed under mysql_derived_prepare when derived is not yet prepared, leading to a find_field_in_table crash.

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-52968 is rated Low Risk (21.8/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.02%). 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-52968

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 2026-04-16 0.06% 0.02% -0.04%
2 2025-11-21 0.16% 0.06% -0.10%
3 2025-11-18 — 0.16% —

Full EPSS history (9 records total)

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

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-52968

OS Trackers for CVE-2023-52968

vendor priority summary link
alpine medium CVE-2023-52968: 1 source package rows (mariadb); 70 state rows across 5 repos (3.19-main, 3.20-main, 3.21-main, 3.22-main, edge-main); fixed 0, open 70. https://security.alpinelinux.org/vuln/CVE-2023-52968
debian unimportant CVE-2023-52968 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-52968
redhat medium — https://access.redhat.com/security/cve/CVE-2023-52968
suse medium CVE-2023-52968 severity moderate: SUSE including 17 source package names (libmariadbd-devel, libmariadbd19, …), 158 product×package rows across 29 product lines (SLES-LTSS-TERADATA 15 SP2, SUSE Linux Enterprise High Performance Computing 15 SP3-LTSS, … (29 product lines)): Known Not Affected 158. https://www.suse.com/security/cve/CVE-2023-52968/
ubuntu medium CVE-2023-52968 medium priority: Ubuntu including 5 source packages (mariadb, mariadb-10.0, mariadb-10.1, mariadb-10.3, mariadb-10.6), 26 status rows across 9 suites (bionic, focal, jammy, noble, oracular, plucky, questing, upstream, xenial): DNE 13, needs-triage 9, ignored 2, not-affected 1, released 1. https://ubuntu.com/security/CVE-2023-52968

Affected software / configurations for CVE-2023-52968

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2023-52968

cvelogic Threat Intelligence