CVE-2020-0618: Authenticated Remote Code Execution in Microsoft SQL Server Reporting Services
- Vendor
- Microsoft Corporation
CVE-2020-0618 is an unsafe deserialization vulnerability in Microsoft SQL Server Reporting Services (SSRS). The Microsoft.Reporting.WebForms.BrowserNavigationCorrector.OnLoad method processes attacker-controlled serialized state using LosFormatter without message authentication code (MAC) validation. A remote user with the low-privileged SSRS Browser role can submit a crafted page request to trigger arbitrary code execution in the context of the Report Server service account. Microsoft addressed the vulnerability in February 2020 by enabling MAC validation for the affected LosFormatter operation.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation allows arbitrary code execution with the permissions of the Report Server service account, potentially compromising the server and accessible data. Attackers can deploy malware, including ransomware, subject to that account's privileges. Exploitation has been associated with TargetCompany/Mallox ransomware activity. Theft of .NET machine keys during a compromise may enable subsequent code execution even after the vulnerability is patched.
Mitigation
If you can’t patch tonight, do this now.
Restrict network access to the SSRS web application to trusted users and systems. Ensure access requires authentication and that anonymous users are not assigned the Browser role. These measures reduce exposure but do not protect against an attacker with an authorized low-privileged account. Web application firewall filtering is not a reliable substitute for patching because malicious requests can be encoded to evade detection.
Remediation
Patch, then assume compromise.
Install the applicable Microsoft security update for CVE-2020-0618 on affected SSRS deployments; the fix was released in February 2020. If exploitation is suspected, perform incident response rather than relying solely on patching, including investigating possible theft of .NET machine keys and addressing compromised secrets that could permit continued access.
Exploits
1 exploit validated by Mallory's analysis. Hidden: 3 rejected by Mallory's analysis as not a working exploit; 1 not yet analyzed, such as Exploit-DB entries.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2020-0618 exploited in the wild?
- Yes. As of Oct 30, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Sep 18, 2024.
- Is there a public exploit for CVE-2020-0618?
- Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2020-0618, the earliest disclosed Feb 11, 2020.
- Is there a patch for CVE-2020-0618?
- Install the applicable Microsoft security update for CVE-2020-0618 on affected SSRS deployments; the fix was released in February 2020. If exploitation is suspected, perform incident response rather than relying solely on patching, including investigating possible theft of .NET machine keys and addressing compromised secrets that could permit continued access.
- What products are affected by CVE-2020-0618?
- Microsoft Corporation Sql Server.
- How severe is CVE-2020-0618?
- CVE-2020-0618 has a CVSS v3.1 score of 8.8 (High) and an EPSS score of 99.0% (100th percentile) as of Oct 30, 2026.
Recent activity
11 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.