Security readout for executives and security teams
Plain-English summary
This issue affects Red Hat OpenShift Enterprise 3.2 in a specific multi-tenant SDN configuration. An authenticated user who can run certain source-to-image builds may reach network resources on pods that should be isolated in other namespaces, weakening tenant separation.
Executive priority
Treat this as a targeted platform isolation issue, not a broad internet-facing emergency. Prioritize if OpenShift 3.2 hosts multiple tenants or sensitive workloads with user-controlled builds.
Technical view
When multi-tenant SDN is enabled, an s2i build in an isolated namespace can access restricted pod network resources if the builder image contains ONBUILD commands or lacks a tar binary. The source identifies remote authenticated access but provides no CVSS score or CWE.
Likely exposure
Exposure appears limited to Red Hat OpenShift Enterprise 3.2 clusters using multi-tenant SDN where authenticated users can run s2i builds with affected builder-image conditions.
Exploitation context
The CVE record does not indicate public exploitation, and it is not listed as KEV in the provided bundle. Abuse requires authentication and build capability in the affected OpenShift environment.
Researcher notes
The provided sources give the core condition and impact but omit CVSS, CWE, and detailed fixed-version information. Avoid assuming affected products beyond Red Hat OpenShift Enterprise 3.2 and consult RHSA-2016:1094 for remediation specifics.
Mitigation direction
- Review Red Hat RHSA-2016:1094 for fixed packages and vendor guidance.
- Prioritize affected OpenShift Enterprise 3.2 clusters using multi-tenant SDN.
- Restrict s2i build permissions to trusted users until remediation is complete.
- Review builder images using ONBUILD commands or lacking tar.
- Document any compensating controls for tenant isolation risk.
Validation and detection
- Inventory OpenShift Enterprise 3.2 clusters and SDN mode.
- Identify namespaces where untrusted users can run s2i builds.
- Review builder images for ONBUILD usage or missing tar.
- Check whether RHSA-2016:1094 remediation is applied.
- Confirm tenant-isolation assumptions with platform owners.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2016-3708 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- RHSA-2016:1094CVE reference · vendor-advisory, x_refsource_REDHAT
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.