8.8
CWE
416
Advisory Published
CVE Published
Updated

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

First published: Tue Apr 09 2024(Updated: )

Microsoft ODBC Driver for SQL Server Remote Code Execution Vulnerability

Credit: secure@microsoft.com

Affected SoftwareAffected VersionHow to fix
Microsoft ODBC Driver 17 for SQL Server
Microsoft ODBC Driver 17 for SQL Server
Microsoft ODBC Driver 18 for SQL Server
Microsoft ODBC Driver 18 for SQL Server
Microsoft ODBC Driver 18 for SQL Server
Microsoft ODBC Driver 17 for SQL Server
Microsoft SQL Server 2022
Microsoft SQL Server 2019
Microsoft ODBC Driver 13 for SQL Server>=17.0.1.1<17.10.6.1
Microsoft ODBC Driver 13 for SQL Server>=17.0.1.1<17.10.6.1
Microsoft ODBC Driver 13 for SQL Server>=17.0.1.1<17.10.6.1
Microsoft ODBC Driver 13 for SQL Server>=18.0.1.1<18.3.3.1
Microsoft ODBC Driver 13 for SQL Server>=18.0.1.1<18.3.3.1
Microsoft ODBC Driver 13 for SQL Server>=18.0.1.1<18.3.3.1
Microsoft SQL Server>=15.0.2000.5<15.0.2110.4
Microsoft SQL Server>=15.0.4003.23<15.0.4360.2
Microsoft SQL Server>=16.0.1000.6<16.0.1115.1
Microsoft SQL Server>=16.0.4003.1<16.0.4120.1
Microsoft SQL Server
Microsoft SQL Server

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • What is the severity of CVE-2024-29043?

    CVE-2024-29043 has a severity rating of critical due to its potential for remote code execution.

  • How do I fix CVE-2024-29043?

    To mitigate CVE-2024-29043, users should apply the latest patches available for the affected Microsoft ODBC Driver and SQL Server products.

  • Which products are affected by CVE-2024-29043?

    CVE-2024-29043 affects various versions of the Microsoft ODBC Driver and SQL Server including both 17 and 18 series on multiple operating systems.

  • What are the impacts of exploiting CVE-2024-29043?

    Exploiting CVE-2024-29043 can allow an attacker to execute arbitrary code on the affected system, leading to data breaches or system compromise.

  • Is there a workaround for CVE-2024-29043?

    Currently, applying available patches is the recommended method of addressing CVE-2024-29043; there are no known effective workarounds.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203