KB5040942: Security update for SQL Server 2017, GDR branch, July 2024. Native Client OLE DB flaws addressed; unused Stretch DB parts removed
Resolves 37 vulnerabilities: 36 rated Important and one unrated, with none rated Critical. It also removes unused Stretch DB components from SQL Server Setup.
Does it affect you? Applies to: Systems running SQL Server 2017 on the GDR branch; the package is for x64. Installing the update is optional on computers that do not host Microsoft SQL Server Reporting Services.
For servers on the GDR branch: they get security fixes only. Servers that install cumulative updates (CU branch) get a separate update. Which branch am I on?
What changes
Removal 1 change
Stretch DB
-
Unused Stretch DB components are removed from SQL Server Setup.1
Bug reference 3297381; platform: Windows.
Technical details
Data sheet · Security · Downloads · Components Click to collapse or expand
Data sheet
- Released
- 2024-07-09
- Classification
- Security Updates
- Type
- Cumulative update
- Servicing branch
- GDR
- Restart
- Required
- Replaced by
- KB5042217
| Version | Build | Channel |
|---|---|---|
| 2017 | 14.0.2056.2 | General availability |
Security
| Vulnerability | Severity | CVSS |
|---|
The table lists the 0 exploited, publicly disclosed or critical vulnerabilities. See all 37 vulnerabilities →
Downloads (Microsoft Update Catalog)
Sources
Cited passages from Microsoft's official notes (1)
-
1.
Removes unused components from SQL Server Setup.
support.microsoft.com
Checked automatically: 7 of 8 checks passed, 1 quoted passage · compared with Microsoft's page on Oct 20, 2026
- Quotes found in the official pages: passed
- Numbers found in the sources: passed
- Vulnerabilities from the dossier only: passed
- Links to allowed domains only: passed
- Every official change covered: passed
- Readable plain text: passed
- Changes confirmed by the file list: passed
- Sources agree: not passed
A second AI read the text against the sources: correctness 5/5, clarity 4/5, completeness 5/5. How we work
Published by The Update Bureau. Written with AI from Microsoft's own documents, checked by rules and a second AI. How we work · Report a mistake