CVE-2015-3631
Public on
Last Modified:
Insights vulnerability analysis
Description
The CVE Program describes this issue as:
Docker Engine before 1.6.1 allows local users to set arbitrary Linux Security Modules (LSM) and docker_t policies via an image that allows volumes to override files in /proc.
Additional information
- Bugzilla 1219065: docker: volume mounts allow LSM profile escalation
- CWE-642: External Control of Critical State Data
- FAQ: Frequently asked questions about CVE-2015-3631
Common Vulnerability Scoring System (CVSS) Score Details
Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
| Red Hat | NVD | |
|---|---|---|
CVSS v2 Base Score | 4.3 | 3.6 |
Attack Vector | Network | Local |
Access Complexity | Medium | Low |
Authentication | None | None |
Confidentiality Impact | None | None |
Integrity Impact | Partial | Partial |
Availability Impact | None | Partial |
CVSS v2 Vector
Red Hat: AV:N/AC:M/Au:N/C:N/I:P/A:N
NVD: AV:L/AC:L/Au:N/C:N/I:P/A:P
Understanding the Weakness (CWE)
Access Control
Technical Impact: Bypass Protection Mechanism; Gain Privileges or Assume Identity
An attacker could potentially modify the state in malicious ways. If the state is related to the privileges or level of authentication that the user has, then state modification might allow the user to bypass authentication or elevate privileges.
Confidentiality
Technical Impact: Read Application Data
The state variables may contain sensitive information that should not be known by the client.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
By modifying state variables, the attacker could violate the application's expectations for the contents of the state, leading to a denial of service due to an unexpected error condition.
Acknowledgements
Red Hat would like to thank Eric Windisch (Docker project) for reporting this issue.
Frequently Asked Questions
Why is Red Hat's CVSS v3 score or Impact different from other vendors?
My product is listed as "Under investigation" or "Affected", when will Red Hat release a fix for this vulnerability?
What can I do if my product is listed as "Will not fix"?
What can I do if my product is listed as "Fix deferred"?
What is a mitigation?
I have a Red Hat product but it is not in the above list, is it affected?
Why is my security scanner reporting my product as vulnerable to this vulnerability even though my product version is fixed or not affected?
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
