In fuse before versions 2.9.8 and 3.x before 3.2.5, fusermount is vulnerable to a restriction bypass when SELinux is active. This allows non-root users to mount a FUSE file system with the allow_other mount option regardless of whether user_allow_other is set in the fuse configuration. An attacker may use this flaw to mount a FUSE file system, accessible by other users, and trick them into accessing files on that file system, possibly causing Denial of Service or other unspecified effects.
The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action.
Name | Vendor | Start Version | End Version |
---|---|---|---|
Debian_linux | Debian | 8.0 (including) | 8.0 (including) |
Debian_linux | Debian | 9.0 (including) | 9.0 (including) |
Red Hat Enterprise Linux 7 | RedHat | fuse-0:2.9.2-11.el7 | * |
Fuse | Ubuntu | bionic | * |
Fuse | Ubuntu | cosmic | * |
Fuse | Ubuntu | disco | * |
Fuse | Ubuntu | eoan | * |
Fuse | Ubuntu | esm-infra/bionic | * |
Fuse | Ubuntu | esm-infra/xenial | * |
Fuse | Ubuntu | precise/esm | * |
Fuse | Ubuntu | trusty | * |
Fuse | Ubuntu | trusty/esm | * |
Fuse | Ubuntu | upstream | * |
Fuse | Ubuntu | xenial | * |
Fuse3 | Ubuntu | disco | * |
Fuse3 | Ubuntu | eoan | * |
Fuse3 | Ubuntu | upstream | * |
Assuming a user with a given identity, authorization is the process of determining whether that user can access a given resource, based on the user’s privileges and any permissions or other access-control specifications that apply to the resource. When access control checks are not applied consistently - or not at all - users are able to access data or perform actions that they should not be allowed to perform. This can lead to a wide range of problems, including information exposures, denial of service, and arbitrary code execution.