The overlayfs implementation in the linux kernel did not properly validate with respect to user namespaces the setting of file capabilities…
The overlayfs implementation in the linux kernel did not properly validate with respect to user namespaces the setting of file capabilities on files in an underlying file system. Due to the combination of unprivileged user namespaces along with a patch carried in the Ubuntu kernel to allow unprivileged overlay mounts, an attacker could use this to gain elevated privileges.
The product does not properly manage privileges while it is switching between different contexts that have different privileges or spheres of control.
https://cwe.mitre.org/data/definitions/270.html →Open in CWE collection →The product makes files or directories accessible to unauthorized actors, even though they should not be.
https://cwe.mitre.org/data/definitions/552.html →Open in CWE collection →An attack of this type exploits a system's configuration that allows an adversary to either directly access an executable file, for example through shell access; or in a possible worst case allows an adversary to upload a file and then execute it. Web servers, ftp servers, and message oriented middleware systems which have many integration points are particularly vulnerable, because both the programmers and the administrators must be in synch regarding the interfaces and the correct privileges for each interface.
https://capec.mitre.org/data/definitions/17.html →Open in CAPEC collection →An adversary hijacks a privileged thread of execution by injecting malicious code into a running process. By using a privleged thread to do their bidding, adversaries can evade process-based detection that would stop an attack that creates a new process. This can lead to an adversary gaining access to the process's memory and can also enable elevated privileges. The most common way to perform this attack is by suspending an existing thread and manipulating its memory.
https://capec.mitre.org/data/definitions/30.html →Open in CAPEC collection →An attack of this type exploits a system's trust in configuration and resource files. When the executable loads the resource (such as an image file or configuration file) the attacker has modified the file to either execute malicious code directly or manipulate the target process (e.g. application server) to execute based on the malicious configuration parameters. Since systems are increasingly interrelated mashing up resources from local and remote sources the possibility of this attack occurring is high.
https://capec.mitre.org/data/definitions/35.html →Open in CAPEC collection →An adversary exploits well-known locations for resources for the purposes of undermining the security of the target. In many, if not most systems, files and resources are organized in a default tree structure. This can be useful for adversaries because they often know where to look for resources or files that are necessary for attacks. Even when the precise location of a targeted resource may not be known, naming conventions may indicate a small area of the target machine's file tree where the resources are typically located. For example, configuration files are normally stored in the /etc director on Unix systems. Adversaries can take advantage of this to commit other types of attacks.
https://capec.mitre.org/data/definitions/150.html →Open in CAPEC collection →An adversary obtains unauthorized information due to improperly protected files. If an application stores sensitive information in a file that is not protected by proper access control, then an adversary can access the file and search for sensitive information.
https://capec.mitre.org/data/definitions/639.html →Open in CAPEC collection →| Product | Vendor | Status |
|---|---|---|
| linux | Exploited | |
| linux | Exploited | |
| linux | Exploited | |
| linux | Exploited | |
| linux | Exploited | |
| linux | Exploited | |
| linux | Exploited | |
| linux | Exploited | |
| linux | Exploited | |
| linux | Exploited | |
| linux | Exploited | |
| linux | Exploited | |
| linux | Exploited | |
| linux | Exploited | |
| linux | Exploited | |
| linux | Exploited | |
| linux | Exploited | |
| linux | Exploited | |
| linux | Exploited | |
| linux | Exploited |