Bug 1636274 (CVE-2018-8292)
Summary: | CVE-2018-8292 .NET Core: information disclosure due to authentication information exposed in a redirect | ||
---|---|---|---|
Product: | [Other] Security Response | Reporter: | Laura Pardo <lpardo> |
Component: | vulnerability | Assignee: | Red Hat Product Security <security-response-team> |
Status: | CLOSED ERRATA | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | unspecified | CC: | bodavis, dbhole, jolee, kanderso, mvardhan, omajid, 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-09-27 09:43:12 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: | 1636275 |
Description
Laura Pardo
2018-10-04 23:13:00 UTC
This issue has been addressed in the following products: .NET Core on Red Hat Enterprise Linux Via RHSA-2018:2902 https://access.redhat.com/errata/RHSA-2018:2902 rh-dotnet21-dotnet not impacted. We are currently shipping .NET Core Runtime 2.1.7. This looks to have been fixed first in tag v2.1.0. ``` git tag --contains=7e6396b2 v2.1-preview2 v2.1-rc1 v2.1.0 v2.1.1 v2.1.2 v2.1.3 v2.1.4 v2.1.4-dependencies v2.1.5 v2.1.5-dependencies v2.1.6 v2.1.6-dependencies v2.1.7 v2.2.0 v2.2.0-dependencies v2.2.0-preview1 v2.2.0-preview2 v2.2.0-preview3 v2.2.0-preview3-dependencies v2.2.1 v3.0.0-preview.18571.3 ``` rh-dotnet22-dotnet not impacted either. Ships with fix. rh-dotnetcore10-dotnetcore is 1.0.13, which has the fix according to upstream. rh-dotnetcore11-dotnetcore is 1.1.10, which is also fixed according to upstream. *** Bug 1664219 has been marked as a duplicate of this bug. *** |