Skip to content

CVE-2020-0618

Microsoft SQL Server Reporting Services Remote Code Execution

8.8 HIGHActively exploited (CISA KEV)Used in ransomwarePublic exploitEPSS 99.0%
  1. Published11 Feb 2020
  2. Added to CISA KEV18 Sept 2024
  3. Remediation due9 Oct 2024
Actively exploited (CISA KEV)

Microsoft SQL Server Reporting Services contains a deserialization vulnerability when handling page requests incorrectly. An authenticated attacker can exploit this vulnerability to execute code in the context of the Report Server service account.

Added to KEV: 18 Sept 2024Federal remediation due: 9 Oct 2024Used in ransomware

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'.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredLow
User interactionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected products

Microsoft SQL Server2012 · 2014 · 2016

Remediation

No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.

Frequently asked

Is CVE-2020-0618 being actively exploited?

Yes. CVE-2020-0618 is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, added 18 Sept 2024. It has been used in ransomware campaigns.

How severe is CVE-2020-0618?

CVE-2020-0618 has a CVSS 3.1 base score of 8.8, rated high. EPSS estimates a 99.0% probability of exploitation.

Which products are affected by CVE-2020-0618?

Affected products include Microsoft SQL Server.

How do I fix CVE-2020-0618?

Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2020-0618 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. Because it is on the CISA KEV list, a risk for it never ranks below high, and the update that fixes it moves to the Emergency patch lane. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.