3: s2i builds implicitly perform docker builds
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | n/a | affected |
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat OpenShift Container Platform 3.2 | |||
| atomic-openshift-0:3.2.0.44-1.git.0.a4463d9.el7 | cpe:/a:redhat:openshift:3.2::el7 | RHSA-2016:1094 | 2016-05-19T00:00:00Z |
| nodejs-node-uuid-0:1.4.7-1.el7 | cpe:/a:redhat:openshift:3.2::el7 | RHSA-2016:1094 | 2016-05-19T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2016-4729 | Red Hat OpenShift Enterprise 3.2, when multi-tenant SDN is enabled and a build is run in a namespace that would normally be isolated from pods in other namespaces, allows remote authenticated users to access network resources on restricted pods via an s2i build with a builder image that (1) contains ONBUILD commands or (2) does not contain a tar binary. |
No CVSS v4.0
No CVSS v3.1
This CVE is not in the KEV list.
Exploit prediction score: 1.1% (1.140% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.