Skip to content
Fencer Intel
medium 4.3

CVE-2017-15137 json

The OpenShift image import whitelist failed to enforce restrictions correctly when running commands such as "oc tag", for example.

published 2018-07-16 8 y ago modified 2026-06-17 4 mo ago also EUVD-2017-6597

cvss
4.3
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.0%
EPSS 1.0% chance of exploitation in 30 days, percentile 62%
public exploits
0
none known

Summary

The OpenShift image import whitelist failed to enforce restrictions correctly when running commands such as "oc tag", for example. This could allow a user with access to OpenShift to run images from registries that should not be allowed.

Patch / fix

  • v8 openshift 3.9 1:3.14.5.10-25.el7
  • apb openshift 3.9 1.1.15-1.el7
  • runc openshift 3.9 1.0.0-24.rc4.dev.gitc6e4a1e.el7
  • cri-o openshift 3.9 1.9.10-1.git8723732.el7
  • fb303 openshift 3.9 0.9.1-15.el7
  • libuv openshift 3.9 1:1.7.5-3.el7
  • scons openshift 3.9 2.5.1-1.el7
  • kibana openshift 3.9 4.6.4-4.el7

red hat advisories RHBA-2018:0489

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-2017-15137 updated cvss 4.3

atomic-openshift: image import whitelist can be bypassed by creating an imagestream or using oc tag

  • Red Hat OpenShift Container Platform 3.7 atomic-openshift, atomic-openshift-pod, atomic-openshift-node, atomic-openshift-tests, atomic-openshift-master, atomic-openshift-clients, +10 more
    affected: no fix available
  • Red Hat OpenShift Container Platform 3.9 apb 1.1.15-1.el7, cockpit 160-3.el7, libuv 1.7.5-3.el7, scons 2.5.1-1.el7, fb303 0.9.1-15.el7, kibana 4.6.4-4.el7, +481 more
    fixed: vendor fix RHBA-2018:0489
  • Red Hat OpenShift Container Platform 3.10 atomic-openshift, atomic-openshift-pod, atomic-openshift-node, atomic-openshift-tests, atomic-openshift-master, atomic-openshift-clients, +7 more
    not 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.99% chance of exploitation in the next 30 days, higher than 62% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.0 4.3 CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
NVD 3.0 5.3 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:P/A:N

Affected products

  • [UNKNOWN] atomic-openshift

Classification

Weakness
  • CWE-20 Improper Input Validation

References

Sources

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.