Bug 1873451 (CVE-2020-1045) - CVE-2020-1045 dotnet: ASP.NET cookie prefix spoofing vulnerability
Summary: CVE-2020-1045 dotnet: ASP.NET cookie prefix spoofing vulnerability
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2020-1045
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1873452 1873453 1873454
Blocks: 1873276
TreeView+ depends on / blocked
 
Reported: 2020-08-28 11:48 UTC by Stefan Cornelius
Modified: 2021-02-16 19:24 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-09-08 19:17:44 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2020:3697 0 None None None 2020-09-08 18:23:58 UTC
Red Hat Product Errata RHSA-2020:3699 0 None None None 2020-09-08 19:01:47 UTC

Description Stefan Cornelius 2020-08-28 11:48:48 UTC
It was discovered that ASP.NET did not properly decode certain cookie values. A remote attacker could exploit this to bypass the "Cookie Prefixes" security mechanism by sending specially crafted cookies to a vulnerable web application.

Comment 1 Stefan Cornelius 2020-08-28 11:48:54 UTC
Statement:

The "Cookie Prefixes" feature is not used by default in ASP.NET. Successful exploitation likely requires a secondary vulnerability, for example a cross-site scripting issue.

Comment 8 errata-xmlrpc 2020-09-08 18:23:55 UTC
This issue has been addressed in the following products:

  .NET Core on Red Hat Enterprise Linux

Via RHSA-2020:3697 https://access.redhat.com/errata/RHSA-2020:3697

Comment 9 errata-xmlrpc 2020-09-08 19:01:45 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2020:3699 https://access.redhat.com/errata/RHSA-2020:3699

Comment 10 Product Security DevOps Team 2020-09-08 19:17:44 UTC
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):

https://access.redhat.com/security/cve/cve-2020-1045


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