CVE-2023-23384 | Microsoft SQL Server Remote Code Execution Vulnerability

Microsoft SQL Server Remote Code Execution Vulnerability

Published: 2023-04-11 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2023-23384 is rated Moderate Risk (47.4/100): CVSS High severity, with medium exploitation likelihood (EPSS 0.87%). 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-23384

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-06-15 1.53% 0.87% -0.66%
2 2026-04-29 1.32% 1.53% +0.21%
3 2026-04-24 — 1.32% —

Full EPSS history (23 records total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.3 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L 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:N)
No account or special rights needed—anonymous or random user is enough.
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:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
 3.9 3.4 [email protected]
7.3 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L 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:N)
No account or special rights needed—anonymous or random user is enough.
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:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
 3.9 3.4 [email protected]

Weakness enumeration for CVE-2023-23384

Affected software / configurations for CVE-2023-23384

Vendor Product Version Raw CPE
microsoft sql_server 2008 cpe:2.3:a:microsoft:sql_server:2008:r2_sp3:*:*:*:*:*:*
microsoft sql_server 2008 cpe:2.3:a:microsoft:sql_server:2008:sp4:*:*:*:*:x64:*
microsoft sql_server 2012 cpe:2.3:a:microsoft:sql_server:2012:sp4:*:*:*:*:*:*
microsoft sql_server 2014 cpe:2.3:a:microsoft:sql_server:2014:sp3:*:*:*:*:*:*
microsoft sql_server 2016 cpe:2.3:a:microsoft:sql_server:2016:sp3:*:*:*:*:x64:*
microsoft sql_server 2017 cpe:2.3:a:microsoft:sql_server:2017:*:*:*:*:*:x64:*
microsoft sql_server 2019 cpe:2.3:a:microsoft:sql_server:2019:*:*:*:*:*:x64:*
microsoft sql_server 2022 cpe:2.3:a:microsoft:sql_server:2022:*:*:*:*:*:x64:*

References for CVE-2023-23384

cvelogic Threat Intelligence