NVD / CVE Program· CNA kubernetes

CVE-2017-1002101: In 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

Noroxi assessment

Priority: Plan (action score 42/100)

Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
Probability of exploitation in the next 30 days: 13.2% (FIRST EPSS); higher than 96.3% of all records.
Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
Fixed version: kubernetes (Debian:12) 1.7.16+dfsg-1; cri-o (openSUSE:Leap 15.1) 1.17.1-lp151.2.2; cri-tools (openSUSE:Leap 15.1) 1.18.0-lp151.2.1.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Add it to your regular patch cycle. Upgrade to kubernetes (Debian:12) 1.7.16+dfsg-1; cri-o (openSUSE:Leap 15.1) 1.17.1-lp151.2.2; cri-tools (openSUSE:Leap 15.1) 1.18.0-lp151.2.1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In 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 any volume type (including non-privileged pods, subject to file permissions) can access files/directories outside of the volume, including the host's filesystem.

CriticalCVSS 9.6 · v3.0—Proof of concept Fix available

Published: Mar 13, 2018
Updated: Jun 16, 2026
EPSS: 13.2% · 96th percentile
CWE: CWE-59

Report tools

JSON

Action score

Plan

Add it to your regular patch cycle.

CVSS: 38 / 40 · 9.6 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 4 / 30 · 13.2%

CNA vs NVD score

NVD: 9.6
CNA · kubernetes: 8.8; 0.8 point gap

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

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

Get told when this record changes

Not in KEV: no record of exploitation in the wild
Proof of concept exists, no weaponized module
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
kubernetes	kubernetes	cpe:2.3:a:kubernetes:kubernetes

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

Affected versions

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

kubernetes kubernetes1.3.0 and later · up to 1.3.10 inclusive
kubernetes kubernetes1.4.0 and later · up to 1.4.12 inclusive
kubernetes kubernetes1.5.0 and later · up to 1.5.8 inclusive
kubernetes kubernetes1.6.0 and later · up to 1.6.13 inclusive
kubernetes kubernetes1.7.0 and later · before 1.7.14
kubernetes kubernetes1.8.0 and later · before 1.8.9
kubernetes kubernetes1.9.0 and later · before 1.9.4

Versions reported by the vendor

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

Kubernetes Kubernetes
- v1.3.x, v1.4.x, v1.5.x, v1.6.xaffected
- unspecified and later · before v1.7.14affected
- unspecified and later · before v1.8.9affected
- unspecified and later · before v1.9.4affected

Package-level exposure

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

+48

Same product

kubernetes: all records

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-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

Published before and after this one in the same product

← EarlierCVE-2015-7561Aug 7, 2017 · Kubernetes in OpenShift3 allows remote authenticated users to use the private images of other users should they know the name of said image.
12Monitor
← EarlierCVE-2017-1002100Sep 14, 2017 · Default access permissions for Persistent Volumes (PVs) created by the Kubernetes Azure cloud provider in versions 1.6.0 to 1.6.5 are set to
26Monitor
Later →CVE-2017-1002102Mar 13, 2018 · In 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 a secret, configMap, projec
22Monitor

Remediation

Which version to upgrade to

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

Product / package	Fixed version	Source
debian:kubernetes	1.7.16+dfsg-1 · Debian:12	Package registry (OSV)
opensuse:cri-o	1.17.1-lp151.2.2 · openSUSE:Leap 15.1	Package registry (OSV)
opensuse:cri-tools	1.18.0-lp151.2.1 · openSUSE:Leap 15.1	Package registry (OSV)
opensuse:go1.14	1.14-lp151.6.1 · openSUSE:Leap 15.1	Package registry (OSV)
opensuse:kubernetes	1.18.0-lp151.5.1 · openSUSE:Leap 15.1	Package registry (OSV)
red hat:atomic-openshift	0:3.3.1.46.11-1.git.4.e236015.el7 · Red Hat:openshift:3.3::el7	Package registry (OSV)
red hat:atomic-openshift-clients	0:3.3.1.46.11-1.git.4.e236015.el7 · Red Hat:openshift:3.3::el7	Package registry (OSV)
red hat:atomic-openshift-clients-redistributable	0:3.3.1.46.11-1.git.4.e236015.el7 · Red Hat:openshift:3.3::el7	Package registry (OSV)
red hat:atomic-openshift-docker-excluder	0:3.3.1.46.11-1.git.4.e236015.el7 · Red Hat:openshift:3.3::el7	Package registry (OSV)
red hat:atomic-openshift-dockerregistry	0:3.3.1.46.11-1.git.4.e236015.el7 · Red Hat:openshift:3.3::el7	Package registry (OSV)
red hat:atomic-openshift-excluder	0:3.3.1.46.11-1.git.4.e236015.el7 · Red Hat:openshift:3.3::el7	Package registry (OSV)
red hat:atomic-openshift-master	0:3.3.1.46.11-1.git.4.e236015.el7 · Red Hat:openshift:3.3::el7	Package registry (OSV)
red hat:atomic-openshift-node	0:3.3.1.46.11-1.git.4.e236015.el7 · Red Hat:openshift:3.3::el7	Package registry (OSV)
red hat:atomic-openshift-pod	0:3.3.1.46.11-1.git.4.e236015.el7 · Red Hat:openshift:3.3::el7	Package registry (OSV)
red hat:atomic-openshift-sdn-ovs	0:3.3.1.46.11-1.git.4.e236015.el7 · Red Hat:openshift:3.3::el7	Package registry (OSV)
red hat:atomic-openshift-tests	0:3.3.1.46.11-1.git.4.e236015.el7 · Red Hat:openshift:3.3::el7	Package registry (OSV)
red hat:tuned-profiles-atomic-openshift-node	0:3.3.1.46.11-1.git.4.e236015.el7 · Red Hat:openshift:3.3::el7	Package registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

Proof-of-concept repository on GitHub ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
Source	Kind	Date
Proof-of-concept repository on GitHub	stars:34	2018-03-22

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.

PublishedMar 13, 2018
First PoCMar 22, 2018+8 d
TodayOct 27, 2026+3150 d

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.

Credits

All researchers

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

Maxim Ivanov

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.

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

TR-20-273 · Apr 27, 2020(Kubernetes Zafiyeti)

All national notices →

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
A low-privileged account is enough.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: none

Impact can extend beyond the vulnerable component (scope changes).

Attack vector: Network
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Changed
Confidentiality impact: High
Integrity impact: High
Availability impact: None

Weakness class (CWE)

CWE-59 · Improper Link Resolution Before File Access ('Link Following')

CVSS vector

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

nvd-primary

Attack context

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

Attack patterns (CAPEC)

ATT&CK techniques

Change log

Fix✗ → ✓Sep 28, 2026, 10:45 PM UTC

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

References

lists.opensuse.org/opensuse-security-announce/2020-04/msg00041.html

Show all references (2 more)

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

All records