ID CVE-2018-0764
Summary 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.
References
Vulnerable Configurations
  • Microsoft .NET Core 1.0
    cpe:2.3:a:microsoft:.net_core:1.0
  • cpe:2.3:a:microsoft:.net_core:1.1
    cpe:2.3:a:microsoft:.net_core:1.1
  • cpe:2.3:a:microsoft:.net_core:2.0
    cpe:2.3:a:microsoft:.net_core:2.0
  • cpe:2.3:a:microsoft:powershell_core:6.0.0
    cpe:2.3:a:microsoft:powershell_core:6.0.0
  • Microsoft .NET Framework 2.0 Service Pack 2
    cpe:2.3:a:microsoft:.net_framework:2.0:sp2
  • Microsoft .NET Framework Version 3.0 Service Pack 2
    cpe:2.3:a:microsoft:.net_framework:3.0:sp2
  • Microsoft Windows Server 2008 Service Pack 2
    cpe:2.3:o:microsoft:windows_server_2008:-:sp2
  • Microsoft .net Framework 3.5
    cpe:2.3:a:microsoft:.net_framework:3.5
  • cpe:2.3:o:microsoft:windows_10
    cpe:2.3:o:microsoft:windows_10
  • cpe:2.3:o:microsoft:windows_10:1511
    cpe:2.3:o:microsoft:windows_10:1511
  • cpe:2.3:o:microsoft:windows_10:1607
    cpe:2.3:o:microsoft:windows_10:1607
  • Microsoft Windows 10 1703
    cpe:2.3:o:microsoft:windows_10:1703
  • cpe:2.3:o:microsoft:windows_8.1
    cpe:2.3:o:microsoft:windows_8.1
  • Microsoft Windows Server 2012
    cpe:2.3:o:microsoft:windows_server_2012
  • cpe:2.3:o:microsoft:windows_server_2012:r2
    cpe:2.3:o:microsoft:windows_server_2012:r2
  • Microsoft Windows Server 2016
    cpe:2.3:o:microsoft:windows_server_2016
  • Microsoft .net Framework 3.5.1
    cpe:2.3:a:microsoft:.net_framework:3.5.1
  • cpe:2.3:o:microsoft:windows_7:-:sp1
    cpe:2.3:o:microsoft:windows_7:-:sp1
  • cpe:2.3:o:microsoft:windows_server_2008:r2:sp1:-:-:-:-:itanium
    cpe:2.3:o:microsoft:windows_server_2008:r2:sp1:-:-:-:-:itanium
  • cpe:2.3:o:microsoft:windows_server_2008:r2:sp1:-:-:-:-:x64
    cpe:2.3:o:microsoft:windows_server_2008:r2:sp1:-:-:-:-:x64
  • Microsoft .net Framework 4.5.2
    cpe:2.3:a:microsoft:.net_framework:4.5.2
  • cpe:2.3:o:microsoft:windows_7:-:sp1
    cpe:2.3:o:microsoft:windows_7:-:sp1
  • cpe:2.3:o:microsoft:windows_8.1
    cpe:2.3:o:microsoft:windows_8.1
  • Microsoft Windows RT 8.1
    cpe:2.3:o:microsoft:windows_rt_8.1
  • Microsoft Windows Server 2008 Service Pack 2
    cpe:2.3:o:microsoft:windows_server_2008:-:sp2
  • cpe:2.3:o:microsoft:windows_server_2008:r2:sp1:-:-:-:-:x64
    cpe:2.3:o:microsoft:windows_server_2008:r2:sp1:-:-:-:-:x64
  • Microsoft Windows Server 2012
    cpe:2.3:o:microsoft:windows_server_2012
  • cpe:2.3:o:microsoft:windows_server_2012:r2
    cpe:2.3:o:microsoft:windows_server_2012:r2
  • Microsoft .net Framework 4.6
    cpe:2.3:a:microsoft:.net_framework:4.6
  • cpe:2.3:o:microsoft:windows_10
    cpe:2.3:o:microsoft:windows_10
  • Microsoft Windows Server 2008 Service Pack 2
    cpe:2.3:o:microsoft:windows_server_2008:-:sp2
  • Microsoft .NET Framework 4.6.1
    cpe:2.3:a:microsoft:.net_framework:4.6.1
  • cpe:2.3:o:microsoft:windows_10:1511
    cpe:2.3:o:microsoft:windows_10:1511
  • Microsoft .NET Framework 4.6.2
    cpe:2.3:a:microsoft:.net_framework:4.6.2
  • Microsoft .NET Framework 4.7.0
    cpe:2.3:a:microsoft:.net_framework:4.7
  • cpe:2.3:o:microsoft:windows_10:1607
    cpe:2.3:o:microsoft:windows_10:1607
  • Microsoft Windows Server 2016
    cpe:2.3:o:microsoft:windows_server_2016
  • Microsoft .net Framework 4.6
    cpe:2.3:a:microsoft:.net_framework:4.6
  • Microsoft .NET Framework 4.6.1
    cpe:2.3:a:microsoft:.net_framework:4.6.1
  • Microsoft .NET Framework 4.6.2
    cpe:2.3:a:microsoft:.net_framework:4.6.2
  • Microsoft .NET Framework 4.7.0
    cpe:2.3:a:microsoft:.net_framework:4.7
  • cpe:2.3:o:microsoft:windows_7:-:sp1
    cpe:2.3:o:microsoft:windows_7:-:sp1
  • cpe:2.3:o:microsoft:windows_8.1
    cpe:2.3:o:microsoft:windows_8.1
  • Microsoft Windows RT 8.1
    cpe:2.3:o:microsoft:windows_rt_8.1
  • cpe:2.3:o:microsoft:windows_server_2008:r2:sp1:-:-:-:-:x64
    cpe:2.3:o:microsoft:windows_server_2008:r2:sp1:-:-:-:-:x64
  • Microsoft Windows Server 2012
    cpe:2.3:o:microsoft:windows_server_2012
  • cpe:2.3:o:microsoft:windows_server_2012:r2
    cpe:2.3:o:microsoft:windows_server_2012:r2
  • Microsoft .NET Framework 4.7.0
    cpe:2.3:a:microsoft:.net_framework:4.7
  • Microsoft Windows 10 1703
    cpe:2.3:o:microsoft:windows_10:1703
  • Microsoft .NET Framework 4.7.1
    cpe:2.3:a:microsoft:.net_framework:4.7.1
  • Microsoft Windows 10 1709
    cpe:2.3:o:microsoft:windows_10:1709
CVSS
Base: 5.0
Impact:
Exploitability:
CWE CWE-19
CAPEC
  • Overflow Buffers
    Buffer Overflow attacks target improper or missing bounds checking on buffer operations, typically triggered by input injected by an attacker. As a consequence, an attacker is able to write past the boundaries of allocated buffer regions in memory, causing a program crash or potentially redirection of execution as per the attackers' choice.
  • XML Nested Payloads
    Applications often need to transform data in and out of the XML format by using an XML parser. It may be possible for an attacker to inject data that may have an adverse effect on the XML parser when it is being processed. By nesting XML data and causing this data to be continuously self-referential, an attacker can cause the XML parser to consume more resources while processing, causing excessive memory consumption and CPU utilization. An attacker's goal is to leverage parser failure to his or her advantage. In most cases this type of an attack will result in a denial of service due to an application becoming unstable, freezing, or crash. However it may be possible to cause a crash resulting in arbitrary code execution, leading to a jump from the data plane to the control plane [R.230.1].
  • XML Oversized Payloads
    Applications often need to transform data in and out of the XML format by using an XML parser. It may be possible for an attacker to inject data that may have an adverse effect on the XML parser when it is being processed. By supplying oversized payloads in input vectors that will be processed by the XML parser, an attacker can cause the XML parser to consume more resources while processing, causing excessive memory consumption and CPU utilization, and potentially cause execution of arbitrary code. An attacker's goal is to leverage parser failure to his or her advantage. In many cases this type of an attack will result in a denial of service due to an application becoming unstable, freezing, or crash. However it is possible to cause a crash resulting in arbitrary code execution, leading to a jump from the data plane to the control plane [R.231.1].
  • XML Client-Side Attack
    Client applications such as web browsers that process HTML data often need to transform data in and out of the XML format by using an XML parser. It may be possible for an attacker to inject data that may have an adverse effect on the XML parser when it is being processed. These adverse effects may include the parser crashing, consuming too much of a resource, executing too slowly, executing code supplied by an attacker, allowing usage of unintended system functionality, etc. An attacker's goal is to leverage parser failure to his or her advantage. In some cases it may be possible to jump from the data plane to the control plane via bad data being passed to an XML parser. [R.484.1]
  • XML Parser Attack
    Applications often need to transform data in and out of the XML format by using an XML parser. It may be possible for an attacker to inject data that may have an adverse effect on the XML parser when it is being processed. These adverse effects may include the parser crashing, consuming too much of a resource, executing too slowly, executing code supplied by an attacker, allowing usage of unintended system functionality, etc. An attacker's goal is to leverage parser failure to his or her advantage. In some cases it may be possible to jump from the data plane to the control plane via bad data being passed to an XML parser. [R.99.1]
msbulletin via4
bulletin_SOURCE_FILE https://portal.msrc.microsoft.com/api/security-guidance/en-us/
cves_url https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2018-0764
impact Denial of Service
knowledgebase_SOURCE_FILE
knowledgebase_id
name Microsoft .NET Framework 4.6/4.6.1/4.6.2/4.7
publishedDate 2018-01-09T08:00:00
severity Important
nessus via4
  • NASL family Red Hat Local Security Checks
    NASL id REDHAT-RHSA-2018-0379.NASL
    description An update for rh-dotnet20-dotnet, rh-dotnetcore10-dotnetcore, and rh-dotnetcore11-dotnetcore is now available for .NET Core on Red Hat Enterprise Linux. Red Hat Product Security has rated this update as having a security impact of Moderate. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) in the References section. .NET Core is a managed software framework. It implements a subset of the .NET framework APIs and includes a CLR implementation. New versions of .NET Core that address several security vulnerabilities are now available. The updated versions are .NET Core 1.0.9, 1.1.6, and 2.0.5. Security Fix(es) : * .NET Core: Improper processing of XML documents can cause a denial of service (CVE-2018-0764) For more details about the security issue(s), including the impact, a CVSS score, and other related information, refer to the CVE page(s) listed in the References section.
    last seen 2019-02-21
    modified 2018-11-10
    plugin id 107114
    published 2018-03-02
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=107114
    title RHEL 7 : .NET Core on Red Hat Enterprise Linux (RHSA-2018:0379)
  • NASL family MacOS X Local Security Checks
    NASL id MACOSX_MS18_JAN_DOTNET_CORE.NASL
    description The Microsoft .NET Core runtime installed on the remote macOS or Mac OS X host is missing a security update. It is, therefore, affected by multiple vulnerabilities : - A security feature bypass in X509 Certificate Validation allows an attacker to present a certificate that is marked as invalid for a specific use, but a component uses it for that purpose. (CVE-2018-0786) - A denial of service vulnerability exists due to improper processing of 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 Core application. (CVE-2018-0764)
    last seen 2019-02-21
    modified 2018-07-14
    plugin id 105729
    published 2018-01-10
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=105729
    title Security Update for .NET Core (January 2018) (macOS)
  • NASL family Windows : Microsoft Bulletins
    NASL id SMB_NT_MS18_JAN_4055266.NASL
    description The .NET Framework installation on the remote host is missing a security update. It is, therefore, affected by the following vulnerabilities: - 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. (CVE-2018-0764) - A security feature bypass vulnerability exists when Microsoft .NET Framework (and .NET Core) components do not completely validate certificates. An attacker could present a certificate that is marked invalid for a specific use, but the component uses it for that purpose. This action disregards the Enhanced Key Usage taggings. (CVE-2018-0786)
    last seen 2019-02-21
    modified 2018-08-03
    plugin id 105731
    published 2018-01-10
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=105731
    title Security and Quality Rollup for .NET Framework (January 2018)
  • NASL family Windows
    NASL id SMB_NT_MS18_JAN_DOTNET_CORE.NASL
    description The remote Windows host has an installation of .NET Core with a version less than 2.0.5. Therefore, the host is affected by multiple vulnerabilities : - A security feature bypass in X509 Certificate Validation allows an attacker to present a certificate that is marked as invalid for a specific use, but a component uses it for that purpose. (CVE-2018-0786) - A denial of service vulnerability exists due to improper processing of 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 Core application. (CVE-2018-0764)
    last seen 2019-02-21
    modified 2018-07-30
    plugin id 105730
    published 2018-01-10
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=105730
    title Security Update for .NET Core (January 2018)
redhat via4
advisories
rhsa
id RHSA-2018:0379
refmap via4
bid 102387
confirm https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2018-0764
sectrack 1040152
Last major update 09-01-2018 - 20:29
Published 09-01-2018 - 20:29
Last modified 25-03-2019 - 15:17
Back to Top