LiveActive security incident?Get immediate response
CVE Record

CVE-2017-1002100: Default access permissions for Persistent Volumes (PVs) created by the Kubernetes Azure cloud provider in v...

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 "container" which exposes a URI that can be accessed without authentication on the public internet. Access to the URI string requires privileged access to the Kubernetes cluster or authenticated access to the Azure portal.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Kubernetes 1.6.0 through 1.6.5 could create Azure-backed Persistent Volumes with overly open default permissions. The storage URI was reachable without authentication from the public internet if someone obtained it. Getting that URI reportedly required privileged cluster access or authenticated Azure portal access, reducing broad opportunistic exposure.

Executive priority

Prioritize this for legacy Azure Kubernetes environments or historical incident review. Current exposure is unlikely unless old clusters, migrated storage, or unchanged Azure containers remain accessible.

Technical view

The Kubernetes Azure cloud provider set Persistent Volume permissions to "container" by default in affected 1.6.x releases. That exposed a publicly accessible URI for the backing Azure storage container. The source bundle does not provide CVSS, CWE, a named patch, or confirmed exploitation evidence.

Likely exposure

Likely limited to organizations that ran Kubernetes 1.6.0 through 1.6.5 with the Azure cloud provider and created Persistent Volumes during that period.

Exploitation context

No KEV listing or provided source states active exploitation. Abuse depends on obtaining the exposed URI, which the CVE description says requires privileged Kubernetes access or authenticated Azure portal access.

Researcher notes

Evidence is sparse in the provided bundle: no CVSS, CWE, exploit confirmation, or explicit fix details are included. The key security issue is public unauthenticated reachability of Azure PV storage when the URI is known.

Mitigation direction

  • Review Kubernetes advisory and issue for vendor-confirmed remediation guidance.
  • Inventory Azure-backed PVs created by Kubernetes 1.6.0 through 1.6.5.
  • Check affected Azure storage containers for public container-level access.
  • Restrict exposed containers according to vendor and cloud-provider guidance.
  • Treat exposed storage contents as potentially disclosed if public access existed.

Validation and detection

  • Confirm whether any clusters used Kubernetes 1.6.0 through 1.6.5 on Azure.
  • Identify Persistent Volumes provisioned by the Kubernetes Azure cloud provider.
  • Review Azure storage access settings for container-level public exposure.
  • Check whether exposed URIs appeared in logs, tickets, documentation, or portals.
  • Document affected data types and retention period for risk assessment.
Prepared
Confidence
medium
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Container behavior lookup

The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2017-1002100 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
KubernetesKubernetesv1.6.0, unspecifiedListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.