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
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2016-3708
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1330735
Blocks: 1331230 1335624
TreeView+ depends on / blocked
 
Reported: 2016-04-28 04:11 UTC by Kurt Seifried
Modified: 2021-02-17 03:58 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-05-20 00:21:20 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:1094 0 normal SHIPPED_LIVE Important: Red Hat OpenShift Enterprise 3.2 security update 2016-05-20 00:12:27 UTC

Description Kurt Seifried 2016-04-28 04:11:59 UTC 
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 04:12:11 UTC 
Acknowledgments:

Name: Ben Parees (Red Hat)
Comment 2 Clayton Coleman 2016-04-28 20:10:22 UTC 
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 20:10:38 UTC 
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 20:13:32 UTC 
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.