Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2024-37339: CWE-822: Untrusted Pointer Dereference in Microsoft Microsoft SQL Server 2017 (GDR)

0
High
VulnerabilityCVE-2024-37339cvecve-2024-37339cwe-822
Published: Tue Sep 10 2024 (09/10/2024, 16:53:38 UTC)
Source: CVE Database V5
Vendor/Project: Microsoft
Product: Microsoft SQL Server 2017 (GDR)

Description

CVE-2024-37339 is a high-severity remote code execution vulnerability in Microsoft SQL Server 2017 (GDR) related to untrusted pointer dereference in the Native Scoring component. It allows an attacker with low privileges to execute arbitrary code remotely without user interaction. The vulnerability impacts confidentiality, integrity, and availability of affected systems. No known exploits are currently in the wild, but the ease of exploitation and critical impact make timely patching essential. This vulnerability affects version 14. 0. 0 of SQL Server 2017 (GDR). Organizations using this version should prioritize mitigation to prevent potential compromise. Countries with significant deployment of Microsoft SQL Server 2017 and critical infrastructure reliance on SQL Server are at higher risk. Mitigation involves applying security updates once available and restricting access to SQL Server Native Scoring services.

AI-Powered Analysis

AILast updated: 02/26/2026, 05:11:56 UTC

Technical Analysis

CVE-2024-37339 is a vulnerability identified in Microsoft SQL Server 2017 (GDR), specifically version 14.0.0, involving an untrusted pointer dereference (CWE-822) in the Native Scoring component. This flaw allows an attacker with low privileges (PR:L) to remotely execute arbitrary code (RCE) without requiring user interaction (UI:N). The vulnerability is exploitable over the network (AV:N) with low attack complexity (AC:L), and it affects confidentiality, integrity, and availability (C:H/I:H/A:H) of the system. The scope is unchanged (S:U), meaning the vulnerability affects only the vulnerable component and does not extend privileges beyond it. The vulnerability was reserved in June 2024 and published in September 2024, with no known exploits in the wild yet. The Native Scoring feature is used for machine learning model scoring within SQL Server, and improper handling of pointers leads to memory corruption, enabling code execution. The lack of user interaction and low complexity make this vulnerability particularly dangerous in environments where SQL Server is exposed to untrusted networks or users. No official patch links are currently provided, indicating that mitigation may rely on forthcoming updates or workarounds.

Potential Impact

If exploited, this vulnerability could allow attackers to execute arbitrary code remotely on affected SQL Server instances, potentially leading to full system compromise. This jeopardizes the confidentiality of sensitive data stored in databases, the integrity of data and applications running on the server, and the availability of critical database services. Attackers could deploy malware, exfiltrate data, or disrupt business operations. Given SQL Server's widespread use in enterprise environments, including finance, healthcare, government, and retail sectors, the impact could be severe and far-reaching. The requirement for low privileges lowers the barrier for exploitation, increasing risk. Organizations with exposed SQL Server Native Scoring services or insufficient network segmentation are particularly vulnerable. The absence of known exploits currently provides a window for proactive defense, but the high CVSS score indicates a critical risk once exploit code becomes available.

Mitigation Recommendations

1. Monitor Microsoft security advisories closely and apply official patches immediately once released for SQL Server 2017 (GDR) version 14.0.0. 2. Restrict network access to SQL Server Native Scoring components by implementing strict firewall rules and network segmentation to limit exposure to untrusted networks. 3. Employ the principle of least privilege by ensuring that accounts interacting with SQL Server have minimal permissions necessary, reducing the risk of exploitation via low-privilege accounts. 4. Enable and review detailed logging and monitoring for unusual activity related to SQL Server processes, especially those involving Native Scoring. 5. Consider disabling or isolating the Native Scoring feature if it is not required for business operations until a patch is available. 6. Conduct regular vulnerability assessments and penetration testing focused on SQL Server environments to detect potential exploitation attempts. 7. Educate database administrators and security teams about this vulnerability and ensure incident response plans include scenarios involving SQL Server RCE attacks.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.1
Assigner Short Name
microsoft
Date Reserved
2024-06-05T20:19:26.777Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 699f6c66b7ef31ef0b563ab8

Added to database: 2/25/2026, 9:40:54 PM

Last enriched: 2/26/2026, 5:11:56 AM

Last updated: 2/26/2026, 9:18:49 AM

Views: 2

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats