CVE-2015-8945 json
openshift-node in OpenShift Origin 1.1.6 and earlier improperly stores router credentials as envvars in the pod when the --credentials opti…
published 2016-08-05 10 y ago modified 2026-06-17 4 mo ago also EUVD-2015-8801
- cvss
- 5.1
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 31%
- public exploits
- 0
- none known
Summary
openshift-node in OpenShift Origin 1.1.6 and earlier improperly stores router credentials as envvars in the pod when the --credentials option is used, which allows local users to obtain sensitive private key information by reading the systemd journal.
Patch / fix
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-8945 updated cvss 5.5
openshift-origin: Logging of private RSA keys into systemd journal
-
Red Hat OpenShift Enterprise 3 Securitynot affected: vulnerable code not present
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
0.37% chance of exploitation in the next 30 days, higher than 31% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 5.1 | CVSS:3.0/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 1.9 | AV:L/AC:M/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-255 Credentials Management Errors
References
-
github.com
/openshift/origin/issues/3951
patch
-
openwall.com
/lists/oss-security/2016/07/13/9
mailing-list, vdb-entry
-
securityfocus.com
/bid/91776
vdb-entry, third-party-advisory
-
openwall.com
/lists/oss-security/2016/07/13/10
mailing-list, vdb-entry
Sources
- CVE List CVE-2015-8945
- NVD CVE-2015-8945
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.