SSRS Remote Code Execution via Malicious Page Requests
Actively exploited in the wild. Patch or mitigate immediately — don't wait for a maintenance window.
An attacker with a basic user account, remotely over the network, with no user interaction, can fully compromise the system — steal data, tamper with it and take it offline.
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'.
Inferred from the weakness type (CWE) and how the flaw is reached — the techniques an attacker would chain to exploit this. Real-world corroboration appears here as threat intel is folded in.
Corroborated threat activity referencing this CVE — with source and confidence, not inference.
Named threat actors and observed ATT&CK techniques appear here as intel feeds are folded in — the ATT&CK chain above stays inferred until then.
Generated by Wavense from the CVE record — an immediate mitigation and the permanent fix.
Implement network access restrictions to SSRS, allowing connections only from trusted hosts or specific subnets. Deploy a Web Application Firewall (WAF) in front of SSRS to detect and block suspicious request patterns indicative of deserialization attacks. Ensure the SSRS service runs with the principle of least privilege to minimize potential damage if compromised.
The permanent fix involves applying the specific security updates released by Microsoft for CVE-2020-0618. Administrators should consult the official Microsoft Security Update Guide or bulletin for their specific SQL Server and SSRS versions to download and install the required patches promptly. Regular patching cycles are crucial to prevent recurrence.
An unauthenticated attacker can achieve remote code execution on the SQL Server Reporting Services (SSRS) server by sending specially crafted page requests. This allows them to gain full control over the SSRS instance, potentially compromise the underlying operating system, access sensitive report data, and establish a foothold for further internal network penetration, leading to significant data breaches or service disruption.
Other CVEs affecting sql server
A remote code execution vulnerability exists in Microsoft SQL Server when it incorrectly handles processing of internal functions, aka 'Microsoft SQL Server Remote Code Execution Vulnerability'.
The TabStrip ActiveX control in the Common Controls in MSCOMCTL.OCX in Microsoft Office 2003 SP3, Office 2003 Web Components SP3, Office 2007 SP2 and SP3, Office 2010 SP1, SQL Server 2000 SP4, SQL Server 2005 SP4, SQL Server 2008 SP2, SP3, R2, R2 SP1, and R2 SP2, Commerce Server 2002 SP4, Commerce Server 2007 SP2, Commerce Server 2009 Gold and R2, Host Integration Server 2004 SP1, Visual FoxPro 8.0 SP1, Visual FoxPro 9.0 SP2, and Visual Basic 6.0 Runtime allows remote attackers to execute arbitrary code via a crafted (1) document or (2) web page that triggers system-state corruption, aka "MSCOMCTL.OCX RCE Vulnerability."