CVE-2015-7528
published 2016-04-11CVE-2015-7528: Kubernetes before 1.2.0-alpha.5 allows remote attackers to read arbitrary pod logs via a container name.
PriorityP433medium5.3CVSS 3.0
AVNACLPRNUINSUCLINAN
EPSS
2.08%
79.2th percentile
Kubernetes before 1.2.0-alpha.5 allows remote attackers to read arbitrary pod logs via a container name.
Affected
5 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | kubernetes | — | — |
| github.com | kubernetes_kubernetes | >= 0 < 1.2.0 | 1.2.0 |
| kubernetes | kubernetes | <= 1.2.0 | — |
| redhat | openshift | — | — |
| redhat | openshift | — | — |
CVSS provenance
nvdv3.05.3MEDIUMCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
nvdv2.05.0MEDIUMAV:N/AC:L/Au:N/C:P/I:N/A:N
vendor_debian5.3LOW
vendor_redhat5.3MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
Information Exposure in Kubernetes in github.com/kubernetes/kubernetes
osv·2024-08-21
CVE-2015-7528 Information Exposure in Kubernetes in github.com/kubernetes/kubernetes
Information Exposure in Kubernetes in github.com/kubernetes/kubernetes
Information Exposure in Kubernetes in github.com/kubernetes/kubernetes
GHSA
Information Exposure in Kubernetes
ghsa·2022-04-12
CVE-2015-7528 [MEDIUM] CWE-200 Information Exposure in Kubernetes
Information Exposure in Kubernetes
Kubernetes before 1.2.0-alpha.5 allows remote attackers to read arbitrary pod logs via a container name.
OSV
Information Exposure in Kubernetes
osv·2022-04-12
CVE-2015-7528 [MEDIUM] Information Exposure in Kubernetes
Information Exposure in Kubernetes
Kubernetes before 1.2.0-alpha.5 allows remote attackers to read arbitrary pod logs via a container name.
Red Hat
OpenShift: pod log location must validate container if provided
vendor_redhat·2015-11-27·CVSS 5.3
CVE-2015-7528 [MEDIUM] CWE-20 OpenShift: pod log location must validate container if provided
OpenShift: pod log location must validate container if provided
Kubernetes before 1.2.0-alpha.5 allows remote attackers to read arbitrary pod logs via a container name.
It was found that OpenShift's API back end did not verify requests for pod log locations, allowing a pod on a Node to request logs for any other pod on that Node. A remote attacker could use this flaw to view sensitive information via pod logs that they would normally not have access to.
Debian
CVE-2015-7528: kubernetes - Kubernetes before 1.2.0-alpha.5 allows remote attackers to read arbitrary pod lo...
vendor_debian·2015·CVSS 5.3
CVE-2015-7528 [MEDIUM] CVE-2015-7528: kubernetes - Kubernetes before 1.2.0-alpha.5 allows remote attackers to read arbitrary pod lo...
Kubernetes before 1.2.0-alpha.5 allows remote attackers to read arbitrary pod logs via a container name.
Scope: local
bookworm: resolved
bullseye: resolved
forky: resolved
sid: resolved
trixie: resolved
No detection rules found.
No public exploits indexed.
http://rhn.redhat.com/errata/RHSA-2015-2615.htmlhttps://access.redhat.com/errata/RHSA-2015:2544https://github.com/kubernetes/kubernetes/pull/17886https://github.com/kubernetes/kubernetes/releases/tag/v1.2.0-alpha.5https://github.com/openshift/origin/pull/6113http://rhn.redhat.com/errata/RHSA-2015-2615.htmlhttps://access.redhat.com/errata/RHSA-2015:2544https://github.com/kubernetes/kubernetes/pull/17886https://github.com/kubernetes/kubernetes/releases/tag/v1.2.0-alpha.5https://github.com/openshift/origin/pull/6113
2016-04-11
Published