LiveActive security incident?Get immediate response
CVE Record

CVE-2020-0618: A remote code execution vulnerability exists in Microsoft SQL Server Reporting Services when it incorrectly...

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

CriticalCVSS 9.8Known exploitedUpdated
Glexia's TakeSource changedcritical

Security readout for executives and security teams

Plain-English summary

CVE-2020-0618 is a critical remote code execution flaw in Microsoft SQL Server Reporting Services. An unauthenticated network attacker could potentially run code by abusing how Reporting Services handles page requests. CISA lists it in the Known Exploited Vulnerabilities catalog, so this is not only theoretical.

Executive priority

High priority. This is a critical Microsoft server-side RCE with known exploitation in CISA KEV. Prioritize patch validation and exposure reduction for SSRS systems supporting business reporting, finance, operations, or customer-facing workflows.

Technical view

Microsoft describes this as an SSRS remote code execution vulnerability tied to incorrect handling of page requests. The CVSS 3.1 score is 9.8 with network attack vector, low complexity, no privileges, and no user interaction. The associated weakness is CWE-502, deserialization of untrusted data.

Likely exposure

Organizations running affected Microsoft SQL Server Reporting Services versions, especially internet-accessible or broadly reachable SSRS instances, should assume elevated risk until patch status is verified. The provided affected list includes SQL Server 2012 SP4, 2014 SP3, and 2016 SP2 variants.

Exploitation context

CISA KEV inclusion indicates known exploitation. The source bundle does not provide details on exploit method, targeting, scale, or whether exploitation is ongoing. Treat exposed SSRS systems as priority assets for verification and remediation.

Researcher notes

Evidence supports critical unauthenticated network RCE in SSRS and KEV status. The bundle does not include exploit details or exact fixed build numbers. Use MSRC as the authoritative source for affected/fixed versions and update applicability.

Mitigation direction

  • Identify all Microsoft SQL Server Reporting Services deployments.
  • Check each instance against the MSRC CVE-2020-0618 advisory.
  • Apply applicable Microsoft security updates or vendor-directed remediation.
  • Reduce unnecessary network exposure to SSRS instances.
  • Prioritize internet-facing and high-value reporting servers first.

Validation and detection

  • Inventory SSRS versions and service pack/CU/GDR levels.
  • Confirm whether listed affected versions are present.
  • Verify installed security updates against Microsoft guidance.
  • Review exposure paths to SSRS from internet and internal networks.
  • Check logs for unusual SSRS page request activity.
Prepared
Confidence
high
Sources
4

The source record changed after analysis. Treat this automated context as pending refresh.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-502: Code execution behavior lookup

Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-0618 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
Yes
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
4Timeline events
2ADP providers
3Source links

CISA KEV status

Status
Known exploited
Source
CISA-ADP
Date added
KEV reference

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: activeAutomatable: noTechnical Impact: total

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2020-0618Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. Added to KEVCISA-ADP

    CISA Known Exploited Vulnerabilities metadata lists this CVE as known exploited.

  4. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:kevother:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
MicrosoftMicrosoft SQL Server2012 for 32-bit Systems Service Pack 4 (QFE), 2012 for x64-based Systems Service Pack 4 (QFE), 2016 for x64-based Systems Service Pack 2 (CU)Listed
MicrosoftMicrosoft SQL Server 2014 Service Pack 3 for x64-based Systems (GDR)unspecifiedListed
MicrosoftMicrosoft SQL Server 2014 Service Pack 3 for x64-based Systems (CU)unspecifiedListed
MicrosoftMicrosoft SQL Server 2016 for x64-based Systems Service Pack 2 (GDR)unspecifiedListed
MicrosoftMicrosoft SQL Server 2014 Service Pack 3 for 32-bit Systems (GDR)unspecifiedListed
MicrosoftMicrosoft SQL Server 2014 Service Pack 3 for 32-bit Systems (CU)unspecifiedListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-502 · source CWE mapping

Deserialization of Untrusted Data

Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.