Track vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
7.1
CVE-2016-3708: OpenShift 3.2 build can reach other pods
CVE-2016-3708 · published 10 years ago
Summary
When the multi‑tenant network feature is turned on in OpenShift Enterprise 3.2, a user who is logged in can start a source‑to‑image build that connects to pods that should be isolated. This lets the attacker talk to restricted services and potentially steal data. Apply the latest OpenShift updates or disable the multi‑tenant SDN until a patch is installed.
What to do
The CVE record does not list a fixed version. Check the vendor's site or the advisory links below - a fix may already be released.
Affected software
| Vendor | Product | Affected versions |
|---|---|---|
| redhat | openshift |
3.2 cpe:2.3:a:redhat:openshift:3.2:*:*:*:enterprise:*:*:* |
Original advisory text
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...
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.
References
- https://access.redhat.com/errata/RHSA-2016:1094 Vendor Advisory
Internet-facing
60 days
Internal
At next upgrade
- Not known to be exploited
- Needs hands-on effort to exploit (estimated)
- Gives an attacker partial control (estimated)
Type
CWE-284Improper Access Control
Timeline
Published8 Jun 2016
Updated4 Nov 2026
First seen29 Sep 2026
Sources
CVE-2016-3708 · NVD
Track software like this
Free during beta