CVE-2020-25654: Critical severity ClusterLabs Pacemaker vulnerability

Published Oct 14, 2020
·
Updated

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.

Other sources

An ACL bypass flaw was found in Pacemaker. This flaw allows an attacker with a local account on the cluster and in the haclient group to use IPC communication with various daemons to directly perform certain tasks that would be prevented if they had gone through configured ACLs. The highest threat from this vulnerability is to confidentiality, integrity, as well as system availability.

An acl bypass flaw was found in pacemaker. When ACLs are not in use, any user in the haclient group has full access to the configuration, which effectively gives them the ability to run any code as root.

When ACLs are in use, users still must be in the haclient group, but their read and write access to various parts of the configuration is limited by configured ACLs.

The vulnerability is that users may use IPC communication with the various daemons directly to perform certain tasks that they would be prevented by ACLs from doing if they went through the configuration.

Red Hat

Affected Software

9 affected componentsFixes available
redhat/pacemaker<0:1.1.23-1.el7_9.1
0:1.1.23-1.el7_9.1
redhat/pacemaker<0:2.0.4-6.el8_3.1
0:2.0.4-6.el8_3.1
redhat/pacemaker<0:2.0.3-5.el8_2.3
0:2.0.3-5.el8_2.3
redhat/pacemaker<1.1.24
1.1.24
redhat/pacemaker<2.0.5
2.0.5
ClusterLabs Pacemaker<1.1.23
ClusterLabs Pacemaker>=2.0.0<2.0.3
ClusterLabs Pacemaker=2.0.5-rc1
Debian Debian Linux=9.0

Event History

Oct 27, 2020
CVE Published
12:00 AM
Nov 24, 2020
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
DescriptionWeakness

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the vulnerability ID of this security flaw?

The vulnerability ID is CVE-2020-25654.

2

What is the severity level of CVE-2020-25654?

The severity level of CVE-2020-25654 is critical with a CVSS score of 7.2.

3

What is the affected software for CVE-2020-25654?

The affected software for CVE-2020-25654 is Clusterlabs Pacemaker versions up to and including 1.1.23, versions between 2.0.0 and 2.0.3, and version 2.0.5-rc1. It also affects Debian Debian Linux version 9.0.

4

How can an attacker exploit CVE-2020-25654?

An attacker with a local account on the cluster and in the haclient group can use IPC communication with various daemons to directly perform certain tasks that would be prevented if they had gone through configured ACLs.

5

What is the fix for CVE-2020-25654?

The fix for CVE-2020-25654 is to upgrade to Clusterlabs Pacemaker version 1.1.24 or later, or version 2.0.5 or later. For Debian Debian Linux, update to version 9.0 or later.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203