dbcve.org
OpenshiftApplication · Redhat

CVE-2017-15137

MEDIUM · 5.3 CVSS v3.0 Published 2018-07-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The OpenShift image import whitelist mechanism failed to properly enforce registry restrictions when executing commands like 'oc tag', allowing authenticated users to import or reference images from registries that should have been blocked by policy.

MitigationReview and update image import policies to ensure whitelist enforcement works across all OpenShift CLI commands, and audit existing deployments for unauthorized images from restricted registries.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
OpenshiftApplication
Affected:all versions
Openshift Container PlatformApplication
Affected:= 3.9

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if image import policy is configured
    Review the master configuration file (typically /etc/origin/master/master-config.yaml) for the 'imagePolicyConfig' section, specifically looking for 'allowedRegistries' or 'disabledRegistries' settings
    Affected if The environment has a whitelist/blacklist configured and an attacker with authenticated access could potentially bypass these restrictions via 'oc tag' or similar commands
  2. Identify configured registry whitelist
    Run 'oc get imagepolicy -o yaml' or inspect the ImagePolicy API to list all registries explicitly allowed in the system
    Affected if There are registries in the allowed list that should have been blocked, or if any registry is allowed when stricter restrictions were intended
  3. Verify external registry configuration
    Check 'oc get imagesstream -A' to see which images exist in the environment, then cross-reference with 'oc get images' to identify the source registry for each image
    Affected if Images exist in the system that were imported from registries that should have been blocked by policy but were allowed due to the whitelist bypass vulnerability
  4. Audit recent image imports and tag operations
    Review OpenShift audit logs and 'oc get events' for patterns of 'oc tag' or image stream operations that may have imported images from unexpected registries
    Affected if There are records of images being imported or tagged from registries that should have been restricted by policy but were not blocked at the time
  5. Check for legacy or misconfigured registry references
    Examine ImageStream specs with 'oc get is -A -o yaml' to find any images referencing registries that are no longer intended to be permitted
    Affected if Image streams contain tags pointing to registries that the current security policy would block if the whitelist were properly enforced

The environment is affected if image import whitelist policies are configured and authenticated users have access to 'oc tag' or similar import commands, as the vulnerability allows bypassing registry restrictions that should be enforced.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Review and update image import policies to ensure whitelist enforcement works across all OpenShift CLI commands, and audit existing deployments for unauthorized images from restricted registries.

Fix this in Openshift Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-15137 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-15137 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data