Red Hat OpenShift Enterprise 3.2 and 3.1 do not properly validate the origin of a request when anonymous access is granted to a service/proxy or pod/proxy API for a specific pod, which allows remote attackers to access API credentials in the web browser localStorage via an access_token in the query parameter.
References
Link | Resource |
---|---|
https://access.redhat.com/errata/RHSA-2016:1094 | Vendor Advisory |
https://access.redhat.com/errata/RHSA-2016:1095 | Vendor Advisory |
Configurations
Configuration 1 (hide)
|
History
12 Feb 2023, 23:18
Type | Values Removed | Values Added |
---|---|---|
References |
|
|
Summary | Red Hat OpenShift Enterprise 3.2 and 3.1 do not properly validate the origin of a request when anonymous access is granted to a service/proxy or pod/proxy API for a specific pod, which allows remote attackers to access API credentials in the web browser localStorage via an access_token in the query parameter. |
02 Feb 2023, 21:16
Type | Values Removed | Values Added |
---|---|---|
Summary | An origin validation vulnerability was found in OpenShift Enterprise. An attacker could potentially access API credentials stored in a web browser's localStorage if anonymous access was granted to a service/proxy or pod/proxy API for a specific pod, and an authorized access_token was provided in the query parameter. | |
References |
|
Information
Published : 2016-06-08 17:59
Updated : 2023-12-10 11:46
NVD link : CVE-2016-3703
Mitre link : CVE-2016-3703
CVE.ORG link : CVE-2016-3703
JSON object : View
Products Affected
redhat
- openshift
CWE
CWE-284
Improper Access Control