CVE-2020-25654: An ACL bypass flaw was found in pacemaker.
Noroxi assessment
Priority: Monitor (action score 29/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.8% (FIRST EPSS); higher than 79.5% of all records.
- Anyone who can reach it over the internet can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: pacemaker (AlmaLinux:8) 2.0.4-6.el8_3.1; pacemaker-cli (AlmaLinux:8) 2.0.4-6.el8_3.1; pacemaker-cts (AlmaLinux:8) 2.0.4-6.el8_3.1.
Low priority for now. Upgrade to pacemaker (AlmaLinux:8) 2.0.4-6.el8_3.1; pacemaker-cli (AlmaLinux:8) 2.0.4-6.el8_3.1; pacemaker-cts (AlmaLinux:8) 2.0.4-6.el8_3.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Nov 24, 2020
- Updated
- Jun 16, 2026
- EPSS
- 1.8% · 79th percentile
- CWE
- CWE-284
Report tools
Action score
29
Low priority for now.
- CVSS
- 28 / 40 · 7.2 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 1.8%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| clusterlabs | pacemaker | cpe:2.3:a:clusterlabs:pacemaker |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.
n/a pacemaker
- pacemaker 1.1.24-rc1, pacemaker 2.0.5-rc2affected
Affected versions · NVD (4)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- clusterlabs pacemakerbefore 1.1.23
- clusterlabs pacemaker2.0.0 and later · before 2.0.3
- clusterlabs pacemaker2.0.5
- debian debian linux9.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | pacemaker | before 2.0.4-6.el8_3.1 | 2.0.4-6.el8_3.1 |
| AlmaLinux:8 | pacemaker-cli | before 2.0.4-6.el8_3.1 | 2.0.4-6.el8_3.1 |
| AlmaLinux:8 | pacemaker-cts | before 2.0.4-6.el8_3.1 | 2.0.4-6.el8_3.1 |
| AlmaLinux:8 | pacemaker-doc | before 2.0.4-6.el8_3.1 | 2.0.4-6.el8_3.1 |
| AlmaLinux:8 | pacemaker-libs-devel | before 2.0.4-6.el8_3.1 | 2.0.4-6.el8_3.1 |
| AlmaLinux:8 | pacemaker-nagios-plugins-metadata | before 2.0.4-6.el8_3.1 | 2.0.4-6.el8_3.1 |
| AlmaLinux:8 | pacemaker-remote | before 2.0.4-6.el8_3.1 | 2.0.4-6.el8_3.1 |
| Debian:10 | pacemaker | before 2.0.1-5+deb10u1 | 2.0.1-5+deb10u1 |
| Debian:12 | pacemaker | before 2.0.5~rc2-1 | 2.0.5~rc2-1 |
| Debian:9 | pacemaker | before 1.1.24-0+deb9u1 | 1.1.24-0+deb9u1 |
| openSUSE:Leap 15.1 | pacemaker | before 2.0.1+20190417.13d370ca9-lp151.2.16.4 | 2.0.1+20190417.13d370ca9-lp151.2.16.4 |
| openSUSE:Leap 15.2 | pacemaker | before 2.0.4+20200616.2deceaa3a-lp152.2.3.1 | 2.0.4+20200616.2deceaa3a-lp152.2.3.1 |
| Red Hat:enterprise_linux:7::server | pacemaker | before 0:1.1.23-1.el7_9.1 | 0:1.1.23-1.el7_9.1 |
| Red Hat:enterprise_linux:7::server | pacemaker-cli | before 0:1.1.23-1.el7_9.1 | 0:1.1.23-1.el7_9.1 |
| Red Hat:enterprise_linux:7::server | pacemaker-cluster-libs | before 0:1.1.23-1.el7_9.1 | 0:1.1.23-1.el7_9.1 |
| Red Hat:enterprise_linux:7::server | pacemaker-cts | before 0:1.1.23-1.el7_9.1 | 0:1.1.23-1.el7_9.1 |
| Red Hat:enterprise_linux:7::server | pacemaker-debuginfo | before 0:1.1.23-1.el7_9.1 | 0:1.1.23-1.el7_9.1 |
| Red Hat:enterprise_linux:7::server | pacemaker-doc | before 0:1.1.23-1.el7_9.1 | 0:1.1.23-1.el7_9.1 |
| Red Hat:enterprise_linux:7::server | pacemaker-libs | before 0:1.1.23-1.el7_9.1 | 0:1.1.23-1.el7_9.1 |
| Red Hat:enterprise_linux:7::server | pacemaker-libs-devel | before 0:1.1.23-1.el7_9.1 | 0:1.1.23-1.el7_9.1 |
| Red Hat:enterprise_linux:7::server | pacemaker-nagios-plugins-metadata | before 0:1.1.23-1.el7_9.1 | 0:1.1.23-1.el7_9.1 |
| Red Hat:enterprise_linux:7::server | pacemaker-remote | before 0:1.1.23-1.el7_9.1 | 0:1.1.23-1.el7_9.1 |
| Red Hat:enterprise_linux:8::appstream | pacemaker | before 0:2.0.4-6.el8_3.1 | 0:2.0.4-6.el8_3.1 |
| Red Hat:enterprise_linux:8::appstream | pacemaker-cli-debuginfo | before 0:2.0.4-6.el8_3.1 | 0:2.0.4-6.el8_3.1 |
+36
Same product
clusterlabs: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-3885A use-after-free flaw was found in pacemaker up to and including version 2.0.1 which could result in certain sensitive information to be…31Monitor
- CVE-2018-16877A flaw was found in the way pacemaker's client-server authentication was implemented in versions up to and including 2.0.0.31Monitor
- CVE-2016-7035An authorization flaw was found in Pacemaker before 1.1.16, where it did not properly guard its IPC interface.31Monitor
Published before and after this one in the same product
- ← EarlierCVE-2016-7797Mar 24, 2017 · Pacemaker before 1.1.15, when using pacemaker remote, might allow remote attackers to cause a denial of service (node disconnection) via an…31Monitor
- ← EarlierCVE-2018-16878Apr 18, 2019 · A flaw was found in pacemaker up to and including version 2.0.1.22Monitor
- ← EarlierCVE-2011-5271Nov 12, 2019 · Pacemaker before 1.1.6 configure script creates temporary files insecurely22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| almalinux:pacemaker | 2.0.4-6.el8_3.1 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:pacemaker-cli | 2.0.4-6.el8_3.1 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:pacemaker-cts | 2.0.4-6.el8_3.1 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:pacemaker-doc | 2.0.4-6.el8_3.1 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:pacemaker-libs-devel | 2.0.4-6.el8_3.1 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:pacemaker-nagios-plugins-metadata | 2.0.4-6.el8_3.1 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:pacemaker-remote | 2.0.4-6.el8_3.1 · AlmaLinux:8 | Package registry (OSV) |
| debian:pacemaker | 2.0.5~rc2-1 · Debian:12 | Package registry (OSV) |
| opensuse:pacemaker | 2.0.4+20200616.2deceaa3a-lp152.2.3.1 · openSUSE:Leap 15.2 | Package registry (OSV) |
| red hat:pacemaker | 0:2.0.3-5.el8_2.3 · Red Hat:rhel_eus:8.2::appstream | Package registry (OSV) |
| red hat:pacemaker-cli | 0:2.0.3-5.el8_2.3 · Red Hat:rhel_eus:8.2::highavailability | Package registry (OSV) |
| red hat:pacemaker-cli-debuginfo | 0:2.0.3-5.el8_2.3 · Red Hat:rhel_eus:8.2::appstream | Package registry (OSV) |
| red hat:pacemaker-cluster-libs | 0:2.0.3-5.el8_2.3 · Red Hat:rhel_eus:8.2::appstream | Package registry (OSV) |
| red hat:pacemaker-cluster-libs-debuginfo | 0:2.0.3-5.el8_2.3 · Red Hat:rhel_eus:8.2::appstream | Package registry (OSV) |
| red hat:pacemaker-cts | 0:2.0.3-5.el8_2.3 · Red Hat:rhel_eus:8.2::highavailability | Package registry (OSV) |
| red hat:pacemaker-debuginfo | 0:2.0.3-5.el8_2.3 · Red Hat:rhel_eus:8.2::appstream | Package registry (OSV) |
| red hat:pacemaker-debugsource | 0:2.0.3-5.el8_2.3 · Red Hat:rhel_eus:8.2::appstream | Package registry (OSV) |
| red hat:pacemaker-libs | 0:2.0.3-5.el8_2.3 · Red Hat:rhel_eus:8.2::appstream | Package registry (OSV) |
| red hat:pacemaker-libs-debuginfo | 0:2.0.3-5.el8_2.3 · Red Hat:rhel_eus:8.2::appstream | Package registry (OSV) |
| red hat:pacemaker-remote-debuginfo | 0:2.0.3-5.el8_2.3 · Red Hat:rhel_eus:8.2::appstream | Package registry (OSV) |
| red hat:pacemaker-schemas | 0:2.0.3-5.el8_2.3 · Red Hat:rhel_eus:8.2::appstream | Package registry (OSV) |
| suse:pacemaker | 2.0.4+20200616.2deceaa3a-3.3.1 · SUSE:Linux Enterprise High Availability Extension 15 SP2 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- Administrator privileges are required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-284 · Improper Access ControlCVSS vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Embedding Scripts within ScriptsCAPEC-19likelihood: High · High
- Malicious Logic InsertionCAPEC-441likelihood: Medium · High
- Modification of Windows Service ConfigurationCAPEC-478likelihood: Low · High
- Malicious Root CertificateCAPEC-479likelihood: Low · Low
- Intent SpoofCAPEC-502
- WebView ExposureCAPEC-503
- Data Injected During ConfigurationCAPEC-536likelihood: Low · High
- Incomplete Data Deletion in a Multi-Tenant EnvironmentCAPEC-546likelihood: Low · Medium
ATT&CK techniques
- RootkitT1014
- Obfuscated Files or Information: Embedded PayloadsT1027.009
- Boot or Logon Initialization ScriptsT1037
- Taint shared contentT1080
- Server Software Component: Terminal Services DLLT1505.005
- Pre-OS Boot:BootkitT1542.003
- Create or Modify System ProcessT1543
- Create or Modify System Process: Launch AgentT1543.001
- Create or Modify System Process:Windows ServiceT1543.003
- Create or Modify System Process: Launch DaemonT1543.004
- Event Triggered Execution:Change Default File AssociationT1546.001
- Event Triggered Execution:.bash_profile and .bashrcT1546.004
- Event Triggered Execution: Accessibility FeaturesT1546.008
- Event Triggered Execution: Installer PackagesT1546.016
- Boot or Logon Autostart ExecutionT1547
- Boot or Logon Autostart Execution:Kernel Modules and ExtensionsT1547.006
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.