CVE-2018-0765
dotnet: Improper processing of XML documents can allow a remote attacker to cause a denial of service
Overview
Description
A denial of service vulnerability exists when .NET and .NET Core improperly process XML documents, aka ".NET and .NET Core Denial of Service Vulnerability." This affects Microsoft .NET Framework 2.0, Microsoft .NET Framework 3.0, Microsoft .NET Framework 4.7.1, Microsoft .NET Framework 4.6/4.6.1/4.6.2/4.7/4.7.1, Microsoft .NET Framework 4.5.2, Microsoft .NET Framework 4.7/4.7.1, Microsoft .NET Framework 4.6, Microsoft .NET Framework 3.5, Microsoft .NET Framework 3.5.1, Microsoft .NET Framework 4.6/4.6.1/4.6.2, Microsoft .NET Framework 4.6.2/4.7/4.7.1, .NET Core 2.0, Microsoft .NET Framework 4.7.2.
Source: OX vulnerability database
Severity
7.5 · HIGH
CVSS 3.0 base score, scored by NVD.
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Weakness: CWE-611
Affected packages · 1
| Ecosystem | Package | Vulnerable | Fixed in |
|---|---|---|---|
| NuGet | System.Security.Cryptography.Xml | <4.4.2 | 4.4.2 |
Open a package to see all its vulnerabilities.
Operating systems
No Linux distribution reports this ID.
References
- www.securityfocus.com http://www.securityfocus.com/bid/104060
- www.securitytracker.com http://www.securitytracker.com/id/1040851
- access.redhat.com https://access.redhat.com/security/cve/CVE-2018-0765
- github.com https://github.com/advisories/GHSA-35hc-x2cw-2j4v
- github.com https://github.com/dotnet/announcements/issues/67
- nvd.nist.gov https://nvd.nist.gov/vuln/detail/CVE-2018-0765
- portal.msrc.microsoft.com https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2018-0765
- www.cve.org https://www.cve.org/CVERecord?id=CVE-2018-0765
OX Radar and Response Center
Find threats in your stack.
OX Radar can check high-priority threats, like critical package CVEs, against your context.
Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.