Bug 1660632 (CVE-2019-0545) - CVE-2019-0545 .NET Core: NCL - SocketsHttpHandler mishandling 1xx response as a final response leads to info disclosure
Summary: CVE-2019-0545 .NET Core: NCL - SocketsHttpHandler mishandling 1xx response as...
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2019-0545
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1660643
TreeView+ depends on / blocked
 
Reported: 2018-12-18 21:18 UTC by Laura Pardo
Modified: 2021-02-16 22:38 UTC (History)
9 users (show)

Fixed In Version: dotnet 2.1.7, dotnet 2.2.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-09-27 09:27:07 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2019:0040 0 None None None 2019-01-09 08:52:51 UTC

Description Laura Pardo 2018-12-18 21:18:52 UTC 
On .NET Core, we mishandle 1xx (includes 100-Continue) response as a final response on SocketsHttpHandler, which will constitute a cross-origin information disclosure vulnerability in case the client multiplexes requests to different origins onto a single persistent connection: the real final response to the first request will be used as a response for a different request on the same connection. (a well behaved server can cause information disclosure as well).
Comment 3 errata-xmlrpc 2019-01-09 08:52:50 UTC 
This issue has been addressed in the following products:

  .NET Core on Red Hat Enterprise Linux

Via RHSA-2019:0040 https://access.redhat.com/errata/RHSA-2019:0040
Comment 4 Laura Pardo 2019-03-15 16:13:17 UTC 
References:

https://github.com/dotnet/announcements/issues/94
https://github.com/dotnet/corefx/issues/34428
https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-0545
Comment 5 Laura Pardo 2019-03-15 16:13:20 UTC 
Acknowledgments:

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