Microsoft SQL Server 2012 SP4/2014 SP3/2016 SP2 Reporting Services deserialization

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
7.4$0-$5k0.00

Summaryinfo

A vulnerability, which was classified as critical, has been found in Microsoft SQL Server 2012 SP4/2014 SP3/2016 SP2. Affected is an unknown function of the component Reporting Services. The manipulation leads to input validation. This vulnerability is referenced as CVE-2020-0618. Remote exploitation of the attack is possible. Furthermore, an exploit is available. Applying a patch is the recommended action to fix this issue.

Detailsinfo

A vulnerability was found in Microsoft SQL Server 2012 SP4/2014 SP3/2016 SP2 (Database Software). It has been rated as critical. This issue affects an unknown functionality of the component Reporting Services. The manipulation with an unknown input leads to a input validation vulnerability. Using CWE to declare the problem leads to CWE-502. The product deserializes untrusted data without sufficiently verifying that the resulting data will be valid. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

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

The weakness was published 02/11/2020 as confirmed security update guide (Website). The advisory is shared at portal.msrc.microsoft.com. The public release has been coordinated with Microsoft. The identification of this vulnerability is CVE-2020-0618. The attack may be initiated remotely. The successful exploitation needs a simple authentication. Technical details are unknown but a public exploit is available. The advisory points out:

A remote code execution vulnerability exists in Microsoft SQL Server Reporting Services when it incorrectly handles page requests. An attacker who successfully exploited this vulnerability could execute code in the context of the Report Server service account.

A public exploit has been developed by Soroush Dalili (irsdl) in PowerShell and been published 3 days after the advisory. The exploit is available at mdsec.co.uk. It is declared as attacked. We expect the 0-day to have been worth approximately $25k-$100k. The CISA Known Exploited Vulnerabilities Catalog lists this issue since 09/18/2024 with a due date of 10/09/2024:

Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

Applying a patch is able to eliminate this problem. A possible mitigation has been published immediately after the disclosure of the vulnerability.

The vulnerability is also documented in the vulnerability database at Exploit-DB (48816). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.6
VulDB Meta Temp Score: 7.4

VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 8.8
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Deserialization
CWE: CWE-502 / CWE-20
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Access: Public
Status: Attacked
Author: Soroush Dalili (irsdl)
Programming Language: 🔍
Download: 🔍

EPSS Score: 🔍
EPSS Percentile: 🔍

KEV Added: 🔍
KEV Due: 🔍
KEV Remediation: 🔍
KEV Ransomware: 🔍
KEV Notice: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Exploit-DB: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Patch
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Exploit Delay Time: 🔍

Timelineinfo

11/04/2019 🔍
02/11/2020 +99 days 🔍
02/11/2020 +0 days 🔍
02/11/2020 +0 days 🔍
02/14/2020 +3 days 🔍
04/04/2025 +1876 days 🔍

Sourcesinfo

Vendor: microsoft.com

Advisory: 156707
Status: Confirmed
Coordinated: 🔍

CVE: CVE-2020-0618 (🔍)
GCVE (CVE): GCVE-0-2020-0618
GCVE (VulDB): GCVE-100-149885
scip Labs: https://www.scip.ch/en/?labs.20161013

Entryinfo

Created: 02/11/2020 20:53
Updated: 04/04/2025 23:55
Changes: 02/11/2020 20:53 (43), 03/02/2020 14:35 (25), 03/29/2024 14:29 (22), 09/19/2024 03:29 (2), 09/30/2024 17:13 (16), 04/04/2025 23:55 (1)
Complete: 🔍
Committer: misc
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to know what is going to be exploited?

We predict KEV entries!