CVE-2019-1068

A remote code execution vulnerability exists in Microsoft SQL Server when it incorrectly handles processing of internal functions, aka 'Microsoft SQL Server Remote Code Execution Vulnerability'.

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

CVE-2019-1068 is rated High Risk (72.2/100): CVSS High severity, with high exploitation likelihood (EPSS 41.57%, 97th percentile). EPSS ranks this CVE among the most likely to be exploited in the near term. EPSS rose +2.98% over the last day, indicating growing attacker interest. High exploitation likelihood—assess exposure and prioritize 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-2019-1068

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-11-21 38.59% 41.57% +2.98%
2 2025-11-18 41.57% 38.59% -2.98%
3 2025-10-19 — 41.57% —

Full EPSS history (23 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2019-1068

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.8 3.0 HIGH
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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:L)
A normal user session is enough; they don’t have to be admin.
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:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.8 5.9 [email protected]
6.5 2.0 MEDIUM
AV:N/AC:L/Au:S/C:P/I:P/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:S)
A single authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:P)
Partial availability impact.
 8.0 6.4 [email protected]

Weakness enumeration for CVE-2019-1068

Affected software / configurations for CVE-2019-1068

Vendor Product Version Raw CPE
microsoft sql_server 2014 cpe:2.3:a:microsoft:sql_server:2014:sp2:*:*:*:*:*:*
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:sp1:*:*:*:*:x64:*
microsoft sql_server 2016 cpe:2.3:a:microsoft:sql_server:2016:sp2:*:*:*:*:x64:*
microsoft sql_server 2017 cpe:2.3:a:microsoft:sql_server:2017:*:*:*:*:*:x64:*

References for CVE-2019-1068

cvelogic Threat Intelligence