Outdated Microsoft SQL Server
A SQL Server instance is missing Microsoft security updates or runs a release that is out of support.
| Severity | High |
| CVSS 3.1 | 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Open in the calculator |
| CVSS 4.0 | 8.7 CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N Open in the calculator |
| CWE | CWE-1395: Dependency on Vulnerable Third-Party Component |
| OWASP Top 10 | A03:2025 Software Supply Chain Failures |
| MITRE ATT&CK | T1210 Exploitation of Remote Services, T1068 Exploitation for Privilege Escalation |
| Category | Outdated Components |
Description
A Microsoft SQL Server instance has not had the security updates that Microsoft has released for it, or runs a release that has passed the end of its support. Microsoft services each supported SQL Server release through cumulative updates (CUs) and, where needed, general distribution release (GDR) security updates, and publishes the vulnerabilities each one fixes in its Security Update Guide.
An attacker with network access to the instance, typically holding a database login or able to reach it through an application, can use the unfixed vulnerabilities to escalate privileges within SQL Server, run code on the server, or crash the service: past SQL Server vulnerabilities include remote code execution, elevation of privilege that lets a database user gain higher rights within the instance, and flaws in the client drivers and providers installed alongside it. Elevated rights in SQL Server usually lead to operating system command execution, through features such as xp_cmdshell or SQL Server Agent jobs, with the rights of the service account, and to access to every database on the instance. The impact is greatest where the service runs as a privileged domain account or the instance holds sensitive data, and is reduced where network access to the instance is tightly restricted.
The finding is identified from the build number, which an authenticated scan reads from the installation and which can also be retrieved over the network from the instance's pre-login response or the SQL Server Browser service on UDP port 1434, compared with the build that includes each fix. Scanners report one result per missing update. Hosts often run several instances, or shared components such as client drivers, at different update levels, and SQL Server Express instances installed silently with third-party applications are a frequent source of findings because they sit outside normal database management.
Remediation
Apply Microsoft's updates and stay on a supported release:
- Install the latest security update for the instance's release, choosing the cumulative update or GDR package according to the servicing path the instance is already on, as Microsoft's guidance explains, and restart the service. Update every instance on the host and the shared client components.
- Opt in to Microsoft Update, or include SQL Server in WSUS or the organisation's patch management tool; SQL Server security updates are offered through Windows Update only when Microsoft Update is enabled.
- Upgrade instances on releases that have passed end of support to a supported release, or obtain Extended Security Updates where Microsoft offers them.
- Remove unused instances, run the service under a low-privileged account, keep
xp_cmdshelldisabled, and restrict access to the database port to the application servers and administrators that need it.
Confirm the fix by running SELECT @@VERSION; on each instance and comparing the build with the update that fixes each reported CVE.
References
Add This Finding to Your Library
In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.
Free trialYour trial starts when your portal goes live, not when you sign up, so the time you spend setting up does not count. · No card required
Only need the reporting? Our reporting tool is free and open source, with the same library.