CVE-2016-1906
First published: Tue Jan 12 2016(Updated: )
Openshift allows remote attackers to gain privileges by updating a build configuration that was created with an allowed type to a type that is not allowed.
Credit: secalert@redhat.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Kubernetes Dashboard |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2016-1906?
CVE-2016-1906 has a medium severity rating due to its potential for privilege escalation.
How do I fix CVE-2016-1906?
To fix CVE-2016-1906, ensure that build configurations are only created with allowed types as per policy.
What systems are affected by CVE-2016-1906?
CVE-2016-1906 affects OpenShift environments that utilize Kubernetes.
Can I be attacked via CVE-2016-1906 remotely?
Yes, CVE-2016-1906 allows remote attackers to potentially gain higher privileges.
What impact does CVE-2016-1906 have on my OpenShift deployment?
CVE-2016-1906 could lead to unauthorized access or control over applications deploying on OpenShift.
- agent/first-publish-date
- collector/redhat-bugzilla
- source/Red Hat
- alias/CVE-2016-1906
- agent/references
- agent/type
- agent/severity
- agent/author
- agent/weakness
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/event
- agent/source
- agent/softwarecombine
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/kubernetes
- canonical/kubernetes dashboard