PT-2024-8558 · Microsoft · Sql Server 2017+5

Published 2024-11-12 · Updated 2025-07-10 · CVE-2024-49000

Positive Technologies (AI Summary)

CVSS v2.0

10

High

Base vector

AV:N/AC:L/Au:N/C:C/I:C/A:C

Name of the Vulnerable Software and Affected Versions Microsoft SQL Server Native Client versions prior to the fixed version Microsoft SQL Server 2016 through 2019

Description The issue is related to a buffer overflow in the dynamic memory of the Microsoft SQL Server Native Client component. This can allow a remote attacker to execute arbitrary code. There is an urgent need for patching to mitigate the risk of remote exploitation.

Recommendations For Microsoft SQL Server Native Client versions prior to the fixed version, apply the necessary patch to fix the buffer overflow issue. For Microsoft SQL Server 2016 through 2019, verify and deploy the patch across all impacted SQL Server instances to prevent remote exploitation. As a temporary workaround, consider restricting access to the Native Client component until a patch is available.

Fix

RCE

Heap Based Buffer Overflow

Weakness Enumeration

CWE-122

Related Identifiers

BDU:2024-10127

CVE-2024-49000

Affected Products

Sql Server 2016

Sql Server 2017

Sql Server 2018

Sql Server 2019

Sql Server Native Client

Sql Server

References · 13

• https://bdu.fstec.ru/vul/2024-10127 · Security Note
• https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-49000 · Vendor Advisory
• https://bdu.fstec.ru/vul/CVE-2024-49000 · Security Note
• https://msrc.microsoft.com/update-guide/en-US/advisory/CVE-2024-49000 · Vendor Advisory
• https://nvd.nist.gov/vuln/detail/CVE-2024-49000 · Security Note
• https://osv.dev/vulnerability/CVE-2024-49000 · Vendor Advisory
• https://t.me/cvenotify/101831 · Telegram Post
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49000 · Note
• https://vuldb.com/?id.284142 · Note
• https://twitter.com/oktsec/status/1856451440132403654 · Twitter Post
• https://t.me/msrcreports/2060 · Telegram Post
• https://twitter.com/CveFindCom/status/1856397098654257499 · Twitter Post
• https://t.me/msrcreports/2067 · Telegram Post