CVE-2024-28932: Microsoft ODBC Driver for SQL Server Remote Code Execution Vulnerability

Overview

Severity
High (CVSS 8.8)
CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
Category
Remote Code Execution
Exploit Status
Not Exploited
Exploitation Likelihood
Less Likely
Patch Tuesday
2024-Apr
Released
2024-04-09
Last Updated
2024-04-18
EPSS Score
2.98% (percentile: 86.5%)

FAQ

According to the CVSS metric, the attack vector is local (AV:L). Why does the CVE title indicate that this is a remote code execution? The word Remote in the title refers to the location of the attacker. This type of exploit is sometimes referred to as Arbitrary Code Execution (ACE). The attack itself is carried out locally. This means an attacker or victim needs to execute code from the local machine to exploit the vulnerability. How could an attacker exploit this vulnerability? An attacker could exploit the vulnerability by tricking an authenticated user into attempting to connect to a malicious SQL server via ODBC, which could result in the client receiving a malicious networking packet. This could allow the attacker to execute code remotely on the client. According to the CVSS metric, user interaction is required (UI:R). What interaction would the user have to do? An attacker could exploit the vulnerability by tricking an authenticated user (CVSS metric UI:R) into attempting to connect to a malicious SQL server via a connection driver (for example: ODBC and / or OLEDB as applicable). I am running SQL Server on my system. What action do I need to take? Update your relevant version of SQL Server. Any applicable driver fixes are included in those updates. I am running my own application on my system. What action do I need to take? Update your application to use Microsoft ODBC Driver 17 or 18 for SQL Server. Update the drivers to the versions listed on this page, which provide protection against this vulnerability. I am running an application from a software vendor on my system. What action do I need to take? Consult with your application vendor if it is compatible with Microsoft ODBC Driver 17 or 18 for SQL Server. Update the drivers to the versions listed in this page, which provide protection against this vulnerability There are GDR and/or CU (Cumulative Update) updates offered for my version of SQL Server. How do I know which update to use? First, determine you

Affected Products (15)

SQL Server

  • Microsoft SQL Server 2022 for x64-based Systems (CU 12)
  • Microsoft SQL Server 2019 for x64-based Systems (CU 25)
  • Microsoft SQL Server 2019 for x64-based Systems (GDR)
  • Microsoft SQL Server 2022 for x64-based Systems (GDR)
  • Microsoft ODBC Driver 17 for SQL Server on Windows
  • Microsoft ODBC Driver 17 for SQL Server on Linux
  • Microsoft ODBC Driver 17 for SQL Server on MacOS
  • Microsoft ODBC Driver 18 for SQL Server on Windows
  • Microsoft ODBC Driver 18 for SQL Server on Linux
  • Microsoft ODBC Driver 18 for SQL Server on MacOS

Developer Tools

  • Microsoft Visual Studio 2019 version 16.11 (includes 16.0 - 16.10)
  • Microsoft Visual Studio 2022 version 17.9
  • Microsoft Visual Studio 2022 version 17.4
  • Microsoft Visual Studio 2022 version 17.6
  • Microsoft Visual Studio 2022 version 17.8

Security Updates (15)

Acknowledgments

<a href="https://www.twitter.com/guhe120">Yuki Chen</a> with <a href="https://www.cyberkl.com/">Cyber KunLun</a>

Revision History

  • 2024-04-09: Information published.
  • 2024-04-18: Corrected Cumulative Update version numbers and reference KB numbers in the FAQ: &quot;There are GDR and/or CU (Cumulative Update) updates offered for my version of SQL Server. How do I know which update to use?&quot; These are informational changes only.