CVE-2024-49021 json
Microsoft SQL Server Remote Code Execution Vulnerability
published 2024-11-12 23 mo ago modified 2026-06-17 4 mo ago also EUVD-2024-43897
- cvss
- 7.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 55%
- public exploits
- 0
- none known
Summary
Microsoft SQL Server Remote Code Execution Vulnerability
Patch / fix
- Microsoft Microsoft SQL Server 2017 (GDR) 14.0.2070.1
- Microsoft Microsoft SQL Server 2019 (GDR) 15.0.2130.3
- Microsoft Microsoft SQL Server 2016 Service Pack 3 (GDR) 13.0.6455.2
- Microsoft Microsoft SQL Server 2016 Service Pack 3 Azure Connect Feature Pack 13.0.7050.2
- Microsoft Microsoft SQL Server 2017 (CU 31) 14.0.3485.1
- Microsoft Microsoft SQL Server 2022 (GDR) 16.0.1135.2
- Microsoft Microsoft SQL Server 2019 (CU 29) 15.0.4410.1
- Microsoft Microsoft SQL Server 2022 for (CU 15) 16.0.4155.4
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 23 mo ago
Exploit prediction
0.77% chance of exploitation in the next 30 days, higher than 55% 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:N/UI:R/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:N/UI:R/S:U/C:H/I:H/A:H |
Affected products
- Microsoft Microsoft SQL Server 2017 (GDR)
- Microsoft Microsoft SQL Server 2019 (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 2022 (GDR)
- Microsoft Microsoft SQL Server 2019 (CU 29)
- Microsoft Microsoft SQL Server 2022 for (CU 15)
Classification
- Weakness
-
- CWE-416 Use After Free
- Technology feeds
References
-
msrc.microsoft.com
/update-guide/vulnerability/CVE-2024-49021
vendor-advisory, patch
Sources
- CVE List CVE-2024-49021
- NVD CVE-2024-49021
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.