CVE-2023-52970

MariaDB Server 10.4 through 10.5.*, 10.6 through 10.6.*, 10.7 through 10.11.*, 11.0 through 11.0.*, and 11.1 through 11.4.* crashes in Item_direct_view_ref::derived_field_transformer_for_where.

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-52970 is rated Moderate Risk (41.9/100): CVSS Medium severity, with medium exploitation likelihood (EPSS 0.45%). Review affected assets and schedule remediation.

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

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-05-20 0.46% 0.45% -0.01%
2 2026-05-07 0.45% 0.46% +0.01%
3 2026-05-02 — 0.45% —

Full EPSS history (14 records total)

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

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

OS Trackers for CVE-2023-52970

vendor priority summary link
alpine medium CVE-2023-52970: 1 source package rows (mariadb); 20 state rows across 5 repos (3.19-main, 3.20-main, 3.21-main, 3.22-main, edge-main); fixed 0, open 20. https://security.alpinelinux.org/vuln/CVE-2023-52970
debian not yet assigned CVE-2023-52970 not yet assigned 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-52970
redhat medium — https://access.redhat.com/security/cve/CVE-2023-52970
suse medium CVE-2023-52970 severity moderate: SUSE including 73 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, …), 131 product×package rows across 21 product lines (Container suse/mariadb, Container suse/mariadb-client, … (21 product lines)): Fixed 84, Known Not Affected 47. https://www.suse.com/security/cve/CVE-2023-52970/
ubuntu medium CVE-2023-52970 medium priority: Ubuntu including 2 source packages (mariadb, mariadb-10.6), 14 status rows across 7 suites (focal, jammy, noble, oracular, plucky, questing, upstream): DNE 7, released 5, ignored 1, not-affected 1. https://ubuntu.com/security/CVE-2023-52970

Affected software / configurations for CVE-2023-52970

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2023-52970

cvelogic Threat Intelligence