Bug 1626263 (CVE-2018-8409)

Summary:	CVE-2018-8409 .NET: Resource loop in ReadAsync when it is being cancelled while producer allocates memory using GetMemory
Product:	[Other] Security Response	Reporter:	Pedro Sampaio <psampaio>
Component:	vulnerability	Assignee:	Red Hat Product Security <security-response-team>
Status:	CLOSED ERRATA	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	unspecified	CC:	bodavis, dbhole, kanderso, omajid, rjanekov, rwagner, security-response-team
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-06-02 23:24:33 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1626264

Description Pedro Sampaio 2018-09-06 21:33:33 UTC

If ReadAsync is being cancelled while producer allocates memory using GetMemory subsequent ReadAsync calls would never block even if there is no new data available causing a tight loop. ReadAsync would start blocking again when producer calls FlushAsync. Only consumers that do not observe IsCancelled flag on ReadResult are affected. .NET Core ≤ 4.5.0 are believed to be vulnerable.

Comment 3 Sam Fowler 2018-09-14 00:47:57 UTC

Acknowledgments:

Name: Microsoft

Comment 4 Sam Fowler 2018-09-14 00:49:02 UTC

External Reference:

https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2018-8409

Comment 5 Radka Gustavsson 2018-09-14 09:25:21 UTC

This was shipped and can be closed.