CVE-2015-7528: Infoleak
Jordan Liggitt of Atomic OpenShift reports:
UPSTREAM: 17886: pod log location must validate container if provided #6113 has security implications, specifically a running pod could make an API call to view the logs of any pod running on the same Node.
External references:
https://github.com/openshift/origin/pull/6113
Other sources
Kubernetes before 1.2.0-alpha.5 allows remote attackers to read arbitrary pod logs via a container name.
— MITRE
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2015-7528?
CVE-2015-7528 has a medium severity rating due to the potential for unauthorized access to sensitive pod logs.
How do I fix CVE-2015-7528?
To fix CVE-2015-7528, you should upgrade your Kubernetes or OpenShift deployment to the latest version that is beyond 1.2.0-alpha.5.
What software is affected by CVE-2015-7528?
CVE-2015-7528 affects Kubernetes versions before 1.2.0-alpha.5 and Red Hat OpenShift versions 3.0 and 3.1.
What is the impact of CVE-2015-7528?
The impact of CVE-2015-7528 is that remote attackers can read arbitrary pod logs, potentially leading to information disclosure.
Who reported CVE-2015-7528?
CVE-2015-7528 was reported by Jordan Liggitt of Atomic OpenShift.