An ACL bypass flaw was found in pacemaker. An attacker having a local account on the cluster and in the haclient group could use IPC communication with various daemons directly to perform certain tasks that they would be prevented by ACLs from doing if they went through the configuration.
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Pacemaker | Clusterlabs | * | 1.1.23 (excluding) |
| Pacemaker | Clusterlabs | 2.0.0 (including) | 2.0.3 (excluding) |
| Pacemaker | Clusterlabs | 2.0.5-rc1 (including) | 2.0.5-rc1 (including) |
| Red Hat Enterprise Linux 7 | RedHat | pacemaker-0:1.1.23-1.el7_9.1 | * |
| Red Hat Enterprise Linux 8 | RedHat | pacemaker-0:2.0.4-6.el8_3.1 | * |
| Red Hat Enterprise Linux 8.2 Extended Update Support | RedHat | pacemaker-0:2.0.3-5.el8_2.3 | * |
| Pacemaker | Ubuntu | bionic | * |
| Pacemaker | Ubuntu | devel | * |
| Pacemaker | Ubuntu | focal | * |
| Pacemaker | Ubuntu | groovy | * |
| Pacemaker | Ubuntu | trusty | * |
| Pacemaker | Ubuntu | xenial | * |
Access control involves the use of several protection mechanisms such as:
When any mechanism is not applied or otherwise fails, attackers can compromise the security of the product by gaining privileges, reading sensitive information, executing commands, evading detection, etc. There are two distinct behaviors that can introduce access control weaknesses: