How severe is CVE-2017-1002102?

CVE-2017-1002102 has a CVSS 3.x base score of 7.1, rated high severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is none, integrity low, and availability high.

Is CVE-2017-1002102 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (59th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2017-1002102?

CVE-2017-1002102 affects Kubernetes. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2017-1002102?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2017-1002102 published?

CVE-2017-1002102 was published on 2018-03-13 and last updated on 2026-06-17.

CVE-2017-1002102

CVE-2017-1002102 is a high-severity vulnerability in Kubernetes with a CVSS 3.x base score of 7.1. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: High (CVSS 3.x base score 7.1)
CVSS v2: 6.3
EPSS exploit prediction: 1% (59th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Kubernetes
Published: 2018-03-13
Last modified: 2026-06-17

Description

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, projected or downwardAPI volume can trigger deletion of arbitrary files/directories from the nodes where they are running.

Frequently asked questions

What is CVE-2017-1002102?: 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, projected or downwardAPI volume can trigger deletion of arbitrary files/directories from the nodes where they are running.
How severe is CVE-2017-1002102?: CVE-2017-1002102 has a CVSS 3.x base score of 7.1, rated high severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is none, integrity low, and availability high.
Is CVE-2017-1002102 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (59th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2017-1002102?: CVE-2017-1002102 affects Kubernetes. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2017-1002102?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2017-1002102 published?: CVE-2017-1002102 was published on 2018-03-13 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:kubernetes:kubernetes:*:*:*:*:*:*:*:*

More vulnerabilities in Kubernetes

CVE-2018-1002105 — Critical (CVSS 9.8): In all Kubernetes versions prior to v1.10.11, v1.11.5, and v1.12.3, incorrect handling of error responses to proxied…
CVE-2017-1000056 — Critical (CVSS 9.8): Kubernetes version 1.5.0-1.5.4 is vulnerable to a privilege escalation in the PodSecurityPolicy admission plugin…
CVE-2016-1906 — Critical (CVSS 9.8): Openshift allows remote attackers to gain privileges by updating a build configuration that was created with an allowed…
CVE-2023-3955 — High (CVSS 8.8): A security issue was discovered in Kubernetes where a user that can create pods on Windows nodes may be able to…
CVE-2023-3676 — High (CVSS 8.8): A security issue was discovered in Kubernetes where a user that can create pods on Windows nodes may be able to…
CVE-2021-25741 — High (CVSS 8.8): A security issue was discovered in Kubernetes where a user may be able to create a container with subpath volume mounts…

All CVEs affecting Kubernetes →