Lyrie
active-exploitation
ACTIVELY EXPLOITED3 sources verified·4 min read
By Lyrie Threat Intelligence·9/18/2024

What happened

CISA added CVE-2020-0618 to the Known Exploited Vulnerabilities (KEV) catalog on 2024-09-18, confirming in-the-wild exploitation of this bug in Microsoft SQL Server Reporting Services (SSRS) CISA KEV. The entry defines a due date of 2024-10-09 for remediation in federal environments, signaling urgency for patching or mitigation CISA KEV. The vulnerability is a remote code execution (RCE) issue driven by improper deserialization behavior in SSRS when handling page requests, and it can be triggered by an authenticated attacker CISA KEV, NVD CVE-2020-0618.

Why it matters

The flaw centers on deserialization of untrusted data (CWE-502), a class of bugs that frequently yield code execution when an application processes crafted serialized input NVD CVE-2020-0618. In this case, SSRS mishandles certain page requests, letting an authenticated user execute code as the Report Server service account, which is a powerful local context for post-exploitation CISA KEV. Because the vulnerability is now in KEV, exploitation has been observed, and environments with reachable SSRS and any compromised credentials face elevated risk of rapid abuse CISA KEV. The CVE is formally tracked by MITRE, confirming vendor and product scope as Microsoft SQL Server/SSRS, and enabling defenders to correlate detections and patching programs by identifier MITRE CVE-2020-0618.

Even though the attack requires authentication, that barrier is thin when adversaries phish users, reuse stolen credentials, or pivot from adjacent systems; once authenticated, this bug provides direct code execution via SSRS’s vulnerable request handling CISA KEV, NVD CVE-2020-0618. Deserialization attacks are attractive because they trigger early in request processing, often before granular authorization checks, making exploitation fast and repeatable at scale NVD CVE-2020-0618.

Technical detail

CVE-2020-0618 is a Microsoft SQL Server Reporting Services remote code execution vulnerability attributed to unsafe deserialization (CWE-502) in the processing of page requests NVD CVE-2020-0618, CISA KEV. An authenticated attacker can supply data that the SSRS component treats as serialized objects; when the service reconstructs those objects, attacker-controlled code paths are invoked, yielding RCE in the Report Server service account context CISA KEV, NVD CVE-2020-0618. This aligns with the general CWE-502 pattern where untrusted data is deserialized without adequate validation or type safety, enabling gadget chains to execute arbitrary logic NVD CVE-2020-0618.

The affected product family is Microsoft SQL Server with the Reporting Services component, as named in the CVE record and KEV listing, which is the attack surface handling the vulnerable page request flow MITRE CVE-2020-0618, CISA KEV. CISA’s KEV entry explicitly notes the authenticated nature of the exploit and the resulting execution context, which bounds the preconditions and impact level defenders should expect during incident response CISA KEV. The KEV addition is an exploitation signal: organizations should assume active scanning and targeted use of this vector against reachable SSRS surfaces CISA KEV.

Defense

CISA mandates action: apply mitigations per vendor guidance or discontinue use if mitigations are unavailable, with a remediation due date of 2024-10-09 in the KEV entry CISA KEV. Prioritize patching any instance running SSRS, since the vulnerability exists in the page request handling path and leads to RCE when abused by an authenticated actor NVD CVE-2020-0618, CISA KEV.

Interim containment should restrict exposure: ensure SSRS is accessible only to trusted, authenticated users on controlled networks, since the exploit requires authentication but yields code execution on success CISA KEV. Validate inventory and ownership for all SQL Server/SSRS deployments tied to the CVE identifier so patch coverage can be tracked to completion across business units MITRE CVE-2020-0618. Because inclusion in KEV denotes active exploitation, accelerate detection engineering and change control around these systems until updates are verified in production CISA KEV.

For incident readiness, anchor detection to the CVE and CWE: watch for anomalous SSRS interactions indicative of deserialization abuse flows and correlate any suspicious activity to assets running Reporting Services tied to CVE-2020-0618 NVD CVE-2020-0618, MITRE CVE-2020-0618.

Lyrie Verdict

Deserialization RCEs are tailor-made for machine-speed abuse: a compromised agent with credentials can hammer SSRS page request paths until code execution lands in the Report Server service account CISA KEV, NVD CVE-2020-0618. Lyrie’s autonomous detectors lock onto the behavior signature of authenticated SSRS request sequences consistent with unsafe deserialization (CWE-502), escalating when activity clusters against assets mapped to CVE-2020-0618 before operators can even triage NVD CVE-2020-0618, MITRE CVE-2020-0618. This is anti-rogue-AI defense where it counts: autonomous, in-band analytics catching authenticated misuse of SSRS page handling in seconds, and enforcing immediate containment while patches roll out CISA KEV.

Lyrie Verdict

Lyrie autonomously detects and contains machine-speed abuse of SSRS page requests consistent with CWE-502 deserialization in CVE-2020-0618, interrupting authenticated RCE attempts before human response.