Bug 1576631 – CVE-2018-0765 dotnet: Improper processing of XML documents can allow a remote attacker to cause a denial of service

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 1576631 - (CVE-2018-0765) CVE-2018-0765 dotnet: Improper processing of XML documents can allow a remote attacker to cause a denial of service

Summary:	CVE-2018-0765 dotnet: Improper processing of XML documents can allow a remote...

Status:	NEW

Aliases:	CVE-2018-0765

Product:	Security Response
Classification:	Other
Component:	vulnerability (Show other bugs)
Sub Component:
Version:	unspecified
Hardware:	All Linux

Priority	high Severity high
Target Milestone:	---
Target Release:	---
Assigned To:	Red Hat Product Security
QA Contact:
Docs Contact:

URL:
Whiteboard:	impact=important,public=20180508,repo...
Keywords:	Security

Depends On:
Blocks:	1576634
	Show dependency tree / graph

Reported:	2018-05-09 22:01 EDT by Sam Fowler
Modified:	2018-05-09 22:12 EDT (History)
CC List:	7 users (show)

See Also:
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Sam Fowler 2018-05-09 22:01:12 EDT

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.


External References:

https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2018-0765
https://github.com/dotnet/announcements/issues/67

Note You need to log in before you can comment on or make changes to this bug.