Skip to main content
Mallory
HighExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2020-0618: Authenticated Remote Code Execution in Microsoft SQL Server Reporting Services

Published Feb 11, 2020 · Updated 18 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days1 mention · peak 1 in a dayToday
CVSS8.8High · v3.1
EPSS99.0%100th percentile
CISA KEVYesAdded Sep 18, 2024
In the wildActivePer CISA KEV
Vendor
Microsoft Corporation
IdentifiersCVE-2020-0618CWE-502 · Deserialization of Untrusted Data

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

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.

Exposure surface

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.

VendorProductType
Microsoft CorporationSql Serverapplication
FAQ

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.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence1Every report linking this CVE to a named adversary.
Associated malware7Malware families linked to this CVE, with evidence and IOCs.
Detection signatures2YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity5Community discussion across Reddit, Mastodon, and other social sources.