CVE-2015-7528 json
Information Exposure in Kubernetes
published 2016-04-11 10 y ago modified 2026-06-17 4 mo ago also GHSA-mqf3-28j7-3mj6 , GO-2022-0857 , EUVD-2022-1787
- cvss
- 5.3
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.1%
- EPSS 2.1% chance of exploitation in 30 days, percentile 81%
- public exploits
- 0
- none known
Summary
Kubernetes before 1.2.0-alpha.5 allows remote attackers to read arbitrary pod logs via a container name.
Patch / fix
- go github.com/kubernetes/kubernetes 1.2.0
- openshift openshift 3.0 3.0.2.0-0.git.38.7576bc5.el7ose
- openshift-node openshift 3.0 3.0.2.0-0.git.38.7576bc5.el7ose
- atomic-openshift openshift 3.1 3.1.0.4-1.git.15.5e061c3.el7aos
- openshift-master openshift 3.0 3.0.2.0-0.git.38.7576bc5.el7ose
- openshift-clients openshift 3.0 3.0.2.0-0.git.38.7576bc5.el7ose
- openshift-sdn-ovs openshift 3.0 3.0.2.0-0.git.38.7576bc5.el7ose
- atomic-openshift-pod openshift 3.1 3.1.0.4-1.git.15.5e061c3.el7aos
- atomic-openshift-node openshift 3.1 3.1.0.4-1.git.15.5e061c3.el7aos
red hat advisories RHSA-2015:2544
- github.com/kubernetes/kubernetes@afd5649 commit
- github.com/openshift/origin#6113 pull request
- github.com/kubernetes/kubernetes#17886 pull request
- github.com/kubernetes/kubernetes/releases/tag/v1.2.0-alpha.5 release
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2015-7528 updated cvss 4.0
OpenShift: pod log location must validate container if provided
-
Red Hat OpenShift Enterprise 3.0 openshift 3.0.2.0-0.git.38.7576bc5.el7ose, openshift-node 3.0.2.0-0.git.38.7576bc5.el7ose, openshift-master 3.0.2.0-0.git.38.7576bc5.el7ose, openshift-clients 3.0.2.0-0.git.38.7576bc5.el7ose, openshift-sdn-ovs 3.0.2.0-0.git.38.7576bc5.el7ose, tuned-profiles-openshift-node 3.0.2.0-0.git.38.7576bc5.el7ose Red Hat OpenShift Enterprise 3.1 atomic-openshift 3.1.0.4-1.git.15.5e061c3.el7aos, atomic-openshift-pod 3.1.0.4-1.git.15.5e061c3.el7aos, atomic-openshift-node 3.1.0.4-1.git.15.5e061c3.el7aos, atomic-openshift-master 3.1.0.4-1.git.15.5e061c3.el7aos, atomic-openshift-clients 3.1.0.4-1.git.15.5e061c3.el7aos, atomic-openshift-recycle 3.1.0.4-1.git.15.5e061c3.el7aos, +4 morefixed: vendor fix RHSA-2015:2544
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
2.08% chance of exploitation in the next 30 days, higher than 81% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 5.3 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
| GitHub | 3.0 | 5.3 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/kubernetes/kubernetes | <1.2.0 |
1.2.0 |
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
- Technology feeds
References
-
github.com
/openshift/origin/pull/6113
web
-
github.com
/kubernetes/kubernetes/pull/17886
web, patch
-
github.com
/kubernetes/kubernetes/commit/afd56495a1052a3387b81df1786a8d0f51bc8671
web, patch
-
rhn.redhat.com
/errata/RHSA-2015-2615.html
vendor-advisory
-
access.redhat.com
/errata/RHSA-2015:2544
vendor-advisory, web
-
github.com
/kubernetes/kubernetes/releases/tag/v1.2.0-alpha.5
web
-
nvd.nist.gov
/vuln/detail/CVE-2015-7528
advisory
-
access.redhat.com
/errata/RHSA-2015:2615
web
-
access.redhat.com
/security/cve/CVE-2015-7528
web
-
bugzilla.redhat.com
/show_bug.cgi?id=1286745
web
-
github.com
/kubernetes/kubernetes
package
-
rhn.redhat.com
/errata/RHSA-2015-2615.html
web
-
github.com
/advisories/GHSA-mqf3-28j7-3mj6
advisory
Sources
- CVE List CVE-2015-7528
- GitHub Advisory GHSA-mqf3-28j7-3mj6
- NVD CVE-2015-7528
- OSV GO-2022-0857
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.