Skip to content
Fencer Vulns
high 7.8

CVE-2023-21704 json

Microsoft ODBC Driver for SQL Server Remote Code Execution Vulnerability

published 2023-02-14 3 y ago modified 2026-11-02 6 d ago also EUVD-2023-25871

cvss
7.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 34%
public exploits
0
none known

Summary

Microsoft ODBC Driver for SQL Server Remote Code Execution Vulnerability

Patch / fix

  • Microsoft Microsoft SQL Server 2014 Service Pack 3 (CU 4) 12.0.6174.8
  • Microsoft Microsoft SQL Server 2014 Service Pack 3 (GDR) 12.0.6444.4
  • Microsoft Microsoft SQL Server 2016 Service Pack 3 (GDR) 13.0.6430.49
  • Microsoft Microsoft SQL Server 2016 Service Pack 3 Azure Connect Feature Pack 13.0.7024.30
  • Microsoft Microsoft SQL Server 2017 (CU 31) 14.0.3460.9
  • Microsoft Microsoft SQL Server 2017 (GDR) 14.0.2047.8
  • Microsoft Microsoft SQL Server 2019 (CU 18) 15.0.4280.7
  • Microsoft Microsoft SQL Server 2019 (GDR) 15.0.2101.7
  • Microsoft Microsoft SQL Server 2022 (GDR) 16.0.1050.5

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
17 mo ago

Exploit prediction

0.40% chance of exploitation in the next 30 days, higher than 34% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 7.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
CNA 3.1 7.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected products

  • Microsoft Microsoft SQL Server 2014 Service Pack 3 (CU 4)
  • Microsoft Microsoft SQL Server 2014 Service Pack 3 (GDR)
  • Microsoft Microsoft SQL Server 2016 Service Pack 3 (GDR)
  • Microsoft Microsoft SQL Server 2016 Service Pack 3 Azure Connect Feature Pack
  • Microsoft Microsoft SQL Server 2017 (CU 31)
  • Microsoft Microsoft SQL Server 2017 (GDR)
  • Microsoft Microsoft SQL Server 2019 (CU 18)
  • Microsoft Microsoft SQL Server 2019 (GDR)
  • Microsoft Microsoft SQL Server 2022 (GDR)

Classification

Weakness
  • CWE-190 Integer Overflow or Wraparound
Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.