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 1626263 - (CVE-2018-8409) CVE-2018-8409 .NET: Resource loop in ReadAsync when it is being cancelled while producer allocates memory using GetMemory
CVE-2018-8409 .NET: Resource loop in ReadAsync when it is being cancelled whi...
Status: NEW
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
low Severity low
: ---
: ---
Assigned To: Red Hat Product Security
impact=low,public=20180911,reported=2...
: Security
Depends On:
Blocks: 1626264
  Show dependency treegraph
 
Reported: 2018-09-06 17:33 EDT by Pedro Sampaio
Modified: 2018-09-14 05:25 EDT (History)
8 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)

  None (edit)
Description Pedro Sampaio 2018-09-06 17:33:33 EDT
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-13 20:47:57 EDT
Acknowledgments:

Name: Microsoft
Comment 5 Radka Janek 2018-09-14 05:25:21 EDT
This was shipped and can be closed.

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