CVE-2020-0618
HighExploitedPublic exploitA remote code execution vulnerability exists in Microsoft SQL Server Reporting Services when it incorrectly handles page requests, aka 'Microsoft SQL Server Reporting Services Remote Code Execution Vulnerability'.
Published Feb 11, 2020 · Updated Aug 15, 2026
Key Facts
Patch immediately- CVE-2020-0618 is a high-severity vulnerability (CVSS 8.8 v3.1) affecting SQL Server (Microsoft), Microsoft SQL Server 2014 Service Pack 3 for 32-bit Systems (CU), Microsoft SQL Server 2014 Service Pack 3 for 32-bit Systems (GDR) and 3 more products.
- It is exploited in the wild, listed in CISA KEV, Industry KEV feed, CIRCL KEV, ENISA EUVD since Jun 5, 2023 and is known to be used in ransomware campaigns. Public exploit code is available.
- EPSS estimates a 99% probability of exploitation in the next 30 days.
- No fixed version is listed yet; check the vendor advisory for mitigations.
- Brandefense priority: patch immediately, because it is listed as exploited in the wild.
CVSS v3.1
8.8
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (30-day exploit likelihood)
99%
Higher than 99.9% of all scored CVEs
Exploited in the wild
Yes
4 catalog listings, used by ransomware
Public exploit code
Available
Proof-of-concept or weaponized module
Get the full CVE-2020-0618 brief as a PDF
Every affected product and fixed release, exploitation status and a first 24 hours response checklist, emailed within minutes.
Description
A remote code execution vulnerability exists in Microsoft SQL Server Reporting Services when it incorrectly handles page requests, aka 'Microsoft SQL Server Reporting Services Remote Code Execution Vulnerability'.
Known-Exploited Catalog Listings
| Catalog | Added | Remediation due | Ransomware use |
|---|---|---|---|
| CISA KEV | Sep 18, 2024 | Oct 9, 2024 | Known |
| Industry KEV feed | Jun 5, 2023 | Oct 9, 2024 | Known |
| CIRCL KEV | Sep 18, 2024 | Oct 9, 2024 | Not reported |
| ENISA EUVD | Sep 18, 2024 | n/a | Not reported |
Required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Affected Products
9 affected entries in total| Product | Affected versions | Fixed in |
|---|---|---|
| SQL ServerMicrosoft | 2012-sp4, 2014-sp3, 2016-sp2, >= 2012 for 32-bit Systems Service Pack 4 (QFE) | n/a |
| Microsoft SQL Server 2014 Service Pack 3 for 32-bit Systems (CU) | >= unspecified | n/a |
| Microsoft SQL Server 2014 Service Pack 3 for 32-bit Systems (GDR) | >= unspecified | n/a |
| Microsoft SQL Server 2014 Service Pack 3 for x64-based Systems (CU) | >= unspecified | n/a |
| Microsoft SQL Server 2014 Service Pack 3 for x64-based Systems (GDR) | >= unspecified | n/a |
Timeline
Publicly disclosed
Feb 11, 2020
Added to Industry KEV feed
Jun 5, 2023
Added to CISA KEV
Sep 18, 2024
Added to CIRCL KEV
Sep 18, 2024
Added to ENISA EUVD
Sep 18, 2024
Last updated
Aug 15, 2026
Weakness Type
- CWE-502 Deserialization of Untrusted Data
References
- patchhttps://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2020-0618
- exploithttp://packetstormsecurity.com/files/156707/SQL-Server-Reporting-Services-SSRS-ViewState-Deserialization.html
- exploithttp://packetstormsecurity.com/files/159216/Microsoft-SQL-Server-Reporting-Services-2016-Remote-Code-Execution.html
- exploitVulnCheck exploitation report
- exploitMSF ssrs_navcorrector_viewstate.rb
FAQ
Common Questions.
A remote code execution vulnerability exists in Microsoft SQL Server Reporting Services when it incorrectly handles page requests, aka 'Microsoft SQL Server Reporting Services Remote Code Execution Vulnerability'.
Affected: SQL Server (Microsoft) versions 2012-sp4, 2014-sp3, 2016-sp2, >= 2012 for 32-bit Systems Service Pack 4 (QFE); Microsoft SQL Server 2014 Service Pack 3 for 32-bit Systems (CU) versions >= unspecified; Microsoft SQL Server 2014 Service Pack 3 for 32-bit Systems (GDR) versions >= unspecified, among others. The full list is in the CVE brief.
It is exploited in the wild, listed in CISA KEV, Industry KEV feed, CIRCL KEV, ENISA EUVD since Jun 5, 2023 and is known to be used in ransomware campaigns.
Yes. It was added on Sep 18, 2024 with a federal remediation due date of Oct 9, 2024.
Public exploit code is available.
No fixed version is listed yet; check the vendor advisory for mitigations.
Brandefense priority: patch immediately, because it is listed as exploited in the wild.
Is CVE-2020-0618 Running On Your Attack Surface?
Brandefense maps vulnerabilities like this one to your internet-facing assets and tells you exactly where to patch.
Request A Demo