CyberSecBulletin
CVE-2019-1068Exploited in the wildNVD status: Analyzed

Microsoft SQL Server Remote Code Execution

CVE-2019-1068 is a high-severity improper input validation vulnerability in Microsoft SQL Server 2014 Service Pack 2 for 32-bit Systems (GDR) from Microsoft, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. CISA added it to the Known Exploited Vulnerabilities catalogue on August 26, 2026, which means attacks have been observed in the wild.

Patch now

Attackers are already exploiting this vulnerability, according to CISA.

What to do

  1. Update SQL Server 2016 to 13.0.4259.0 or 13.0.4604.0 or 13.0.5101.9 or 13.0.5366.0, whichever matches your release line, or a later version.
  2. Update SQL Server 2017 to 14.0.2027.2 or 14.0.3192.2, whichever matches your release line, or a later version.
  3. CISA's required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
  4. Read the advisory on portal.msrc.microsoft.com for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
MicrosoftMicrosoft SQL Server 2014 Service Pack 2 for 32-bit Systems (GDR)Not specified in the recordNot stated
MicrosoftMicrosoft SQL Server2014 Service Pack 2 for 32-bit Systems (CU); 2014 Service Pack 2 for x64-based Systems (CU); 2016 for x64-based Systems Service Pack 1 (CU); 2017 for x64-based Systems (CU); 2016 for x64-based Systems Service Pack 2 (CU)Not stated
MicrosoftMicrosoft SQL Server 2014 Service Pack 2 for x64-based Systems (GDR)Not specified in the recordNot stated
MicrosoftMicrosoft SQL Server 2016 for x64-based Systems Service Pack 1 (GDR)Not specified in the recordNot stated
MicrosoftMicrosoft SQL Server 2017 for x64-based Systems (GDR)Not specified in the recordNot stated
MicrosoftMicrosoft SQL Server 2016 for x64-based Systems Service Pack 2 (GDR)Not specified in the recordNot stated
MicrosoftMicrosoft SQL Server 2014 Service Pack 3 for x64-based Systems (GDR)Not specified in the recordNot stated
MicrosoftMicrosoft SQL Server 2014 Service Pack 3 for x64-based Systems (CU)Not specified in the recordNot stated
MicrosoftMicrosoft SQL Server 2014 Service Pack 3 for 32-bit Systems (GDR)Not specified in the recordNot stated
MicrosoftMicrosoft SQL Server 2014 Service Pack 3 for 32-bit Systems (CU)Not specified in the recordNot stated
MicrosoftSQL Server2014Not stated
MicrosoftSQL Server 201613.0.4001.0 up to, but not including, 13.0.4259.0; 13.0.4411.0 up to, but not including, 13.0.4604.0; 13.0.5026.0 up to, but not including, 13.0.5101.9; 13.0.5149.0 up to, but not including, 13.0.5366.013.0.4259.0, 13.0.4604.0, 13.0.5101.9, 13.0.5366.0
MicrosoftSQL Server 201714.0.1000.169 up to, but not including, 14.0.2027.2; 14.0.3006.16 up to, but not including, 14.0.3192.214.0.2027.2, 14.0.3192.2

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.18.8HighNVD
CVSS 3.18.8HighCISA (ADP)
CVSS 2.06.5MediumNVD

Official description

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'.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Improper Input Validation

The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

How developers prevent this class of flaw

  • Consider using language-theoretic security (LangSec) techniques that characterize inputs using a formal language and build recognizers for that language. This effectively requires parsing to be a distinct layer that effectively enforces a boundary between raw input and internal data representations, instead of allowing parser code to be scattered throughout the program, where it could be subject to errors or inconsistencies that create weaknesses.
  • Use an input validation framework such as Struts or the OWASP ESAPI Validation API. Note that using a framework does not automatically address all input validation problems; be mindful of weaknesses that could arise from misusing the framework itself (CWE-1173).
  • Understand all the potential areas where untrusted inputs can enter the product, including but not limited to: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide data to the application. Remember that such inputs may be obtained indirectly through API calls.

More Improper Input Validation vulnerabilities (CWE-20)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: active, automatable: no, technical impact: total).
  3. Added to CISA's Known Exploited Vulnerabilities catalogue.
  4. Record last changed materially (score, affected products, status or references).
  5. Deadline for US federal agencies to remediate, set by CISA.

References

Third-party and government advisories

Recent Improper Input Validation vulnerabilities

Spotted an error? Tell us.