Microsoft .NET Framework up to 5.7 XML data processing

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.
6.3$0-$5k0.00

Summaryinfo

A vulnerability was found in Microsoft .NET Framework up to 5.7. It has been classified as problematic. The affected element is an unknown function of the component XML Handler. The manipulation leads to data processing. This vulnerability is uniquely identified as CVE-2018-0764. The attack is possible to be carried out remotely. No exploit exists. Applying a patch is the recommended action to fix this issue.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in Microsoft .NET Framework up to 5.7 (Programming Language Software). This issue affects an unknown code block of the component XML Handler. The manipulation with an unknown input leads to a data processing vulnerability. Using CWE to declare the problem leads to CWE-19. Impacted is availability. The summary by CVE is:

Microsoft .NET Framework 1.1, 2.0, 3.0, 3.5, 3.5.1, 4, 4.5, 4.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2 and 5.7 and .NET Core 1.0. 1.1 and 2.0 allow a denial of service vulnerability due to the way XML documents are processed, aka ".NET and .NET Core Denial Of Service Vulnerability". This CVE is unique from CVE-2018-0765.

The bug was discovered 01/09/2018. The weakness was disclosed 01/09/2018 with Microsoft as confirmed security update guide (Website). The advisory is shared at portal.msrc.microsoft.com. The identification of this vulnerability is CVE-2018-0764 since 12/01/2017. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available. The advisory points out:

A Denial of Service vulnerability exists when .NET, and .NET core, improperly process XML documents. An attacker who successfully exploited this vulnerability could cause a denial of service against a .NET application. A remote unauthenticated attacker could exploit this vulnerability by issuing specially crafted requests to a .NET(or .NET core) application.

The vulnerability scanner Nessus provides a plugin with the ID 105729 (Security Update for .NET Core (January 2018) (macOS)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family MacOS X Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 91427 (Microsoft .NET Framework Security Update January 2018).

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 databases at Tenable (105729) and SecurityFocus (BID 102387†). The entry VDB-111560 is pretty similar. 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: 6.4
VulDB Meta Temp Score: 6.3

VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 7.5
NVD Vector: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Data processing
CWE: CWE-19
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 105729
Nessus Name: Security Update for .NET Core (January 2018) (macOS)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 870324
OpenVAS Name: Microsoft Windows Multiple Vulnerabilities (KB4056892)
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Patch
Status: 🔍

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

Timelineinfo

12/01/2017 🔍
01/09/2018 +39 days 🔍
01/09/2018 +0 days 🔍
01/09/2018 +0 days 🔍
01/09/2018 +0 days 🔍
01/09/2018 +0 days 🔍
01/10/2018 +1 days 🔍
01/10/2018 +0 days 🔍
01/20/2023 +1836 days 🔍

Sourcesinfo

Vendor: microsoft.com

Advisory: RHSA-2018:0379
Researcher: Microsoft
Organization: Microsoft
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2018-0764 (🔍)
GCVE (CVE): GCVE-0-2018-0764
GCVE (VulDB): GCVE-100-111557

OVAL: 🔍

SecurityFocus: 102387 - Microsoft .NET Framework CVE-2018-0764 Remote Denial of Service Vulnerability
SecurityTracker: 1040152

See also: 🔍

Entryinfo

Created: 01/10/2018 14:16
Updated: 01/20/2023 13:34
Changes: 01/10/2018 14:16 (79), 12/28/2019 20:08 (5), 01/29/2021 12:06 (2), 01/29/2021 12:10 (1), 01/20/2023 13:34 (3)
Complete: 🔍
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 ▸

Might our Artificial Intelligence support you?

Check our Alexa App!