Bug 1331229 – CVE-2016-3708 OpenShiftEnterprise 3: s2i builds implicitly perform docker builds

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 1331229 - (CVE-2016-3708) CVE-2016-3708 OpenShiftEnterprise 3: s2i builds implicitly perform docker builds

Summary:	CVE-2016-3708 OpenShiftEnterprise 3: s2i builds implicitly perform docker builds

Status:	CLOSED ERRATA

Aliases:	CVE-2016-3708

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=20160427,repor...
Keywords:	Security

Depends On:	1330735
Blocks:	1331230 1335624
	Show dependency tree / graph

Reported:	2016-04-28 00:11 EDT by Kurt Seifried
Modified:	2016-05-19 20:21 EDT (History)
CC List:	9 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:	A flaw was found in OpenShift Enterprise when multi-tenant SDN is enabled and a build is run within a namespace that would normally be isolated from pods in other namespaces. If an s2i build is run in such an environment the container being built can access network resources on pods that should not be available to it.
Story Points:	---
Clone Of:
Environment:
Last Closed:	2016-05-19 20:21:20 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.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2016:1094	normal	SHIPPED_LIVE	Important: Red Hat OpenShift Enterprise 3.2 security update	2016-05-19 20:12:27 EDT

Groups: None (edit)

Description Kurt Seifried 2016-04-28 00:11:59 EDT

Ben Parees of Red Hat reports:

When an s2i build is run, if the builder image contains ONBUILD commands, or if 
the builder image does not contain a "tar" binary, s2i will construct a 
Dockerfile and docker build it in order to execute the ONBUILD commands or to 
layer the source code into the image for assembly.

This is a problem for openshift because the docker build container is not 
running with network isolation.

Comment 1 Kurt Seifried 2016-04-28 00:12:11 EDT

Acknowledgments:

Name: Ben Parees (Red Hat)

Comment 2 Clayton Coleman 2016-04-28 16:10:22 EDT

This is an issue only when multi-tenant SDN is enabled and the build is run in a namespace that would normally be isolated from pods in other namespaces.  The pod can access normal network functions as if the multitenant SDN was not enabled (equivalent to when the standard SDN function is enabled).

Comment 3 Clayton Coleman 2016-04-28 16:10:38 EDT

This is an issue only when multi-tenant SDN is enabled and the build is run in a namespace that would normally be isolated from pods in other namespaces.  The pod can access normal network functions as if the multitenant SDN was not enabled (equivalent to when the standard SDN function is enabled).

Comment 4 errata-xmlrpc 2016-05-19 16:13:32 EDT

This issue has been addressed in the following products:

  Red Hat OpenShift Enterprise 3.2

Via RHSA-2016:1094 https://access.redhat.com/errata/RHSA-2016:1094

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