pcs before version 0.9.164 and 0.10 is vulnerable to a privilege escalation via authorized user malicious REST call. The REST interface of the pcsd service did not properly sanitize the file name from the /remote/put_file query. If the /etc/booth directory exists, an authenticated attacker with write permissions could create or overwrite arbitrary files with arbitrary data outside of the /etc/booth directory, in the context of the pcsd process.
The product makes files or directories accessible to unauthorized actors, even though they should not be.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Pacemaker_command_line_interface | Clusterlabs | * | 0.9.164 (including) |
| Pacemaker_command_line_interface | Clusterlabs | 0.10 (including) | 0.10 (including) |
| Red Hat Enterprise Linux 7 | RedHat | pcs-0:0.9.162-5.el7_5.1 | * |
| Pcs | Ubuntu | artful | * |
| Pcs | Ubuntu | cosmic | * |
| Pcs | Ubuntu | upstream | * |
Web servers, FTP servers, and similar servers may store a set of files underneath a “root” directory that is accessible to the server’s users. Applications may store sensitive files underneath this root without also using access control to limit which users may request those files, if any. Alternately, an application might package multiple files or directories into an archive file (e.g., ZIP or tar), but the application might not exclude sensitive files that are underneath those directories. In cloud technologies and containers, this weakness might present itself in the form of misconfigured storage accounts that can be read or written by a public or anonymous user.