Bug 1492101 – CVE-2017-1002100 kubernetes: Incorrect default access permissions for Persistent Volumes

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 1492101 - (CVE-2017-1002100) CVE-2017-1002100 kubernetes: Incorrect default access permissions for Persistent Volumes

Summary:	CVE-2017-1002100 kubernetes: Incorrect default access permissions for Persist...

Status:	CLOSED WONTFIX

Aliases:	CVE-2017-1002100

Product:	Security Response
Classification:	Other
Component:	vulnerability (Show other bugs)
Sub Component:
Version:	unspecified
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Red Hat Product Security
QA Contact:
Docs Contact:

URL:
Whiteboard:	impact=moderate,public=20170615,repor...
Keywords:	Security

Depends On:
Blocks:	1492102
	Show dependency tree / graph

Reported:	2017-09-15 09:07 EDT by Adam Mariš
Modified:	2018-04-10 07:41 EDT (History)
CC List:	16 users (show)

See Also:
Fixed In Version:	kubernetes 1.6.6
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2018-04-10 07:41:06 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Adam Mariš 2017-09-15 09:07:54 EDT

A vulnerability has been disclosed in which 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.

Only Kubernetes 1.6.0-1.6.5 installations that have Persistent Volumes (PVs) actively provisioned through the Azure cloud provider are subject to the vulnerability. Clusters without PVs are unaffected. No other form of cluster storage is impacted.

An individual with the full URI of an actively provisioned persistent volume can download the VHD file for that volume. It does not apply retroactively to volumes already deleted from the cluster.

Upstream bug:

https://github.com/kubernetes/kubernetes/issues/47611

Upstream patch:

https://github.com/kubernetes/kubernetes/pull/47605

Note You need to log in before you can comment on or make changes to this bug.