Skip to content
Noroxi
CVE-2016-7075· NVD / CVE Program· CNA redhat

It was found that Kubernetes as used by Openshift Enterprise 3 did not correctly validate X.509 client intermediate certificate host name fi

It was found that Kubernetes as used by Openshift Enterprise 3 did not correctly validate X.509 client intermediate certificate host name fields. An attacker could use this flaw to bypass authentication requirements by using a specially crafted X.509 certificate.

HighCVSS 8.1 · v3.0—No exploit Fix available
Published
Sep 10, 2018
Updated
Jun 16, 2026
EPSS
1.6% · 74th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

32

Monitor

Low priority for now.

CVSS
32 / 40 · 8.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 1.6%

CNA vs NVD score

NVD
8.1
CNA · redhat
7.5
0.6 point gap

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Affected systems

VendorProduct
kuberneteskubernetes
redhatopenshift

Using kubernetes? Add it to your stack and be the first to know about CVEs like this one. (Kubernetes)

Add to my stack

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • kubernetes kubernetesall versions

Versions reported by the vendor

Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.

  • Red Hat OpenShift

    • n/aaffected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12kubernetesbefore 1.5.5+dfsg-11.5.5+dfsg-1
Red Hat:openshift:3.1::el7atomic-openshiftbefore 0:3.1.1.8-1.git.0.d469026.el7aos0:3.1.1.8-1.git.0.d469026.el7aos
Red Hat:openshift:3.1::el7atomic-openshift-clientsbefore 0:3.1.1.8-1.git.0.d469026.el7aos0:3.1.1.8-1.git.0.d469026.el7aos
Red Hat:openshift:3.1::el7atomic-openshift-clients-redistributablebefore 0:3.1.1.8-1.git.0.d469026.el7aos0:3.1.1.8-1.git.0.d469026.el7aos
Red Hat:openshift:3.1::el7atomic-openshift-dockerregistrybefore 0:3.1.1.8-1.git.0.d469026.el7aos0:3.1.1.8-1.git.0.d469026.el7aos
Red Hat:openshift:3.1::el7atomic-openshift-masterbefore 0:3.1.1.8-1.git.0.d469026.el7aos0:3.1.1.8-1.git.0.d469026.el7aos
Red Hat:openshift:3.1::el7atomic-openshift-nodebefore 0:3.1.1.8-1.git.0.d469026.el7aos0:3.1.1.8-1.git.0.d469026.el7aos
Red Hat:openshift:3.1::el7atomic-openshift-podbefore 0:3.1.1.8-1.git.0.d469026.el7aos0:3.1.1.8-1.git.0.d469026.el7aos
Red Hat:openshift:3.1::el7atomic-openshift-recyclebefore 0:3.1.1.8-1.git.0.d469026.el7aos0:3.1.1.8-1.git.0.d469026.el7aos
Red Hat:openshift:3.1::el7atomic-openshift-sdn-ovsbefore 0:3.1.1.8-1.git.0.d469026.el7aos0:3.1.1.8-1.git.0.d469026.el7aos
Red Hat:openshift:3.1::el7tuned-profiles-atomic-openshift-nodebefore 0:3.1.1.8-1.git.0.d469026.el7aos0:3.1.1.8-1.git.0.d469026.el7aos
Red Hat:openshift:3.2::el7atomic-openshiftbefore 0:3.2.1.17-1.git.0.6d01b60.el70:3.2.1.17-1.git.0.6d01b60.el7
Red Hat:openshift:3.2::el7atomic-openshift-clientsbefore 0:3.2.1.17-1.git.0.6d01b60.el70:3.2.1.17-1.git.0.6d01b60.el7
Red Hat:openshift:3.2::el7atomic-openshift-clients-redistributablebefore 0:3.2.1.17-1.git.0.6d01b60.el70:3.2.1.17-1.git.0.6d01b60.el7
Red Hat:openshift:3.2::el7atomic-openshift-dockerregistrybefore 0:3.2.1.17-1.git.0.6d01b60.el70:3.2.1.17-1.git.0.6d01b60.el7
Red Hat:openshift:3.2::el7atomic-openshift-masterbefore 0:3.2.1.17-1.git.0.6d01b60.el70:3.2.1.17-1.git.0.6d01b60.el7
Red Hat:openshift:3.2::el7atomic-openshift-nodebefore 0:3.2.1.17-1.git.0.6d01b60.el70:3.2.1.17-1.git.0.6d01b60.el7
Red Hat:openshift:3.2::el7atomic-openshift-podbefore 0:3.2.1.17-1.git.0.6d01b60.el70:3.2.1.17-1.git.0.6d01b60.el7
Red Hat:openshift:3.2::el7atomic-openshift-recyclebefore 0:3.2.1.17-1.git.0.6d01b60.el70:3.2.1.17-1.git.0.6d01b60.el7
Red Hat:openshift:3.2::el7atomic-openshift-sdn-ovsbefore 0:3.2.1.17-1.git.0.6d01b60.el70:3.2.1.17-1.git.0.6d01b60.el7
Red Hat:openshift:3.2::el7atomic-openshift-testsbefore 0:3.2.1.17-1.git.0.6d01b60.el70:3.2.1.17-1.git.0.6d01b60.el7
Red Hat:openshift:3.2::el7tuned-profiles-atomic-openshift-nodebefore 0:3.2.1.17-1.git.0.6d01b60.el70:3.2.1.17-1.git.0.6d01b60.el7
Red Hat:openshift:3.3::el7atomic-openshiftbefore 0:3.3.0.35-1.git.0.d7bd9b6.el70:3.3.0.35-1.git.0.d7bd9b6.el7
Red Hat:openshift:3.3::el7atomic-openshift-clientsbefore 0:3.3.0.35-1.git.0.d7bd9b6.el70:3.3.0.35-1.git.0.d7bd9b6.el7

+8

Other highest-scoring records for the same primary product.

  • CVE-2018-1002105In all Kubernetes versions prior to v1.10.11, v1.11.5, and v1.12.3, incorrect handling of error responses to proxied upgrade requests in the
    65This week
  • CVE-2019-11248Kubernetes kubelet exposes /debug/pprof info on healthz port
    55Plan
  • CVE-2017-1002101In Kubernetes versions 1.3.x, 1.4.x, 1.5.x, 1.6.x and prior to versions 1.7.14, 1.8.9 and 1.9.4 containers using subpath volume mounts with
    42Plan
  • CVE-2018-1002101In Kubernetes versions 1.9.0-1.9.9, 1.10.0-1.10.5, and 1.11.0-1.11.1, user input was handled insecurely while setting up volume mounts on Wi
    40Plan
  • CVE-2017-1000056Kubernetes version 1.5.0-1.5.4 is vulnerable to a privilege escalation in the PodSecurityPolicy admission plugin resulting in the ability to
    40Plan
  • CVE-2016-1906Openshift allows remote attackers to gain privileges by updating a build configuration that was created with an allowed type to a type that
    40Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:kubernetes1.5.5+dfsg-1 · Debian:12Package registry (OSV)
red hat:atomic-openshift0:3.1.1.8-1.git.0.d469026.el7aos · Red Hat:openshift:3.1::el7Package registry (OSV)
red hat:atomic-openshift-clients0:3.1.1.8-1.git.0.d469026.el7aos · Red Hat:openshift:3.1::el7Package registry (OSV)
red hat:atomic-openshift-clients-redistributable0:3.1.1.8-1.git.0.d469026.el7aos · Red Hat:openshift:3.1::el7Package registry (OSV)
red hat:atomic-openshift-dockerregistry0:3.1.1.8-1.git.0.d469026.el7aos · Red Hat:openshift:3.1::el7Package registry (OSV)
red hat:atomic-openshift-master0:3.1.1.8-1.git.0.d469026.el7aos · Red Hat:openshift:3.1::el7Package registry (OSV)
red hat:atomic-openshift-node0:3.1.1.8-1.git.0.d469026.el7aos · Red Hat:openshift:3.1::el7Package registry (OSV)
red hat:atomic-openshift-pod0:3.1.1.8-1.git.0.d469026.el7aos · Red Hat:openshift:3.1::el7Package registry (OSV)
red hat:atomic-openshift-recycle0:3.1.1.8-1.git.0.d469026.el7aos · Red Hat:openshift:3.1::el7Package registry (OSV)
red hat:atomic-openshift-sdn-ovs0:3.1.1.8-1.git.0.d469026.el7aos · Red Hat:openshift:3.1::el7Package registry (OSV)
red hat:atomic-openshift-tests0:3.2.1.17-1.git.0.6d01b60.el7 · Red Hat:openshift:3.2::el7Package registry (OSV)
red hat:tuned-profiles-atomic-openshift-node0:3.1.1.8-1.git.0.d469026.el7aos · Red Hat:openshift:3.1::el7Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

CVSS vector

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

nvd-primary

Root cause

A certificate validation error is silently swallowed instead of terminating the connection. Often, code added for a test environment makes its way into production.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

kotlin
override fun checkServerTrusted(chain: Array<X509Certificate>, type: String) {  // Left empty for the test environment}

Fixed

kotlin
val client = OkHttpClient.Builder()  .certificatePinner(    CertificatePinner.Builder()      .add("api.sirius.example", "sha256/…")      .build()  ).build()

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records