CVE-2020-0618

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: 8.8High
Exploited in the wild: Yes, in CISA KEV since 18 Sept 2024CISA deadline for US federal agencies: 9 Oct 2024known use in ransomware campaignspublic exploit code
EPSS: 99.0%chance of exploitation in the next 30 daystop 0.1% of scored CVEsFIRST score of 11 Nov 2026
Fix: Patch availablesee the advisories in the references
Published: 11 Feb 2020analysed here 12 Nov 2026

Do first. Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable. (CISA's required action for this KEV entry)

Summary

Triage

Attack surface: Server-side
Exploitable: At runtime
Attack vector: network
Weakness: CWE-502 Insecure Deserialization

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.

Affected products

Products named in our analysis

microsoft:sql_server

Fix and mitigation

WAF and other mitigations

Can a WAF block it? Partly. Insecure deserialization payloads can be built from many different gadget chains, so WAF signatures only catch the known ones.

Also consider: allow-list classes · patch

Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog: Listed since 18 Sept 2024. Known use in ransomware campaigns.
CISA due date: 9 Oct 2024, the remediation deadline for US federal agencies
CISA required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Public exploit code: Yes: 1 on Exploit-DB · 1 Metasploit module · 4 GitHub proofs of concept · 1 Nuclei template
CISA SSVC: exploitation active, automatable no, technical impact totalAssessed by CISA 20 Sept 2024 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

Timeline

11 Feb 2020Published
15 Feb 2020First public exploit or proof of concept3 days later
18 Sept 2024Added to CISA KEV (exploited in the wild)1,677 days (about 5 years) later
20 Sept 2024CISA SSVC assessment: exploitation active2 days later
9 Oct 2024CISA remediation due date (US federal agencies)19 days later
15 Aug 2026CVE record last updated675 days (about 2 years) later
12 Nov 2026Analysed by vulneraibility.com89 days (about 3 months) later

CVSS vector

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

Metric	Value	What it means
Attack vector	NetworkReachable over the internet or any routable network.	Reachable over the internet or any routable network.
Attack complexity	LowRepeatable attack, no special conditions.	Repeatable attack, no special conditions.
Privileges required	LowThe attacker needs basic user privileges.	The attacker needs basic user privileges.
User interaction	NoneNo victim action needed.	No victim action needed.
Scope	UnchangedImpact stays within the vulnerable component.	Impact stays within the vulnerable component.
Confidentiality	HighTotal data disclosure possible.	Total data disclosure possible.
Integrity	HighComplete modification possible.	Complete modification possible.
Availability	HighFull outage possible.	Full outage possible.

Common questions

Is CVE-2020-0618 being exploited?

Yes. CVE-2020-0618 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2020-0618?

CVE-2020-0618 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2020-0618?

Yes. A fix has been recorded for CVE-2020-0618. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2020-0618 affect?

CVE-2020-0618 affects microsoft:sql_server. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVD CVE.org CVE Details Source

4 references in the CVE record, grouped by the tags the record gives them.

Where the data on this page comes from

CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
NVD: CVSS and CPE data
CISA KEV catalog: exploitation, date added, due date
CISA Vulnrichment (ADP): SSVC decision points
FIRST EPSS: exploit probability and percentile
Exploit-DB: published exploits
Metasploit Framework: exploit and scanner modules
Nuclei templates: detection templates
PoC-in-GitHub: GitHub repositories that claim a proof of concept

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.