Pacemaker vulnerabilitiesRanked by how likely they are to be used.
Pacemaker is made by Clusterlabs. We track 10 published vulnerabilities listed under that exact name, across 50 versions. None of them is on the list of flaws known to be exploited today. Clusterlabs lists newer releases under their own names, such as Pacemaker Command Line Interface, so check those pages too.
We keep watching the known-exploited list.
Is Pacemaker listed under other names? Yes.
Clusterlabs also lists Pacemaker under more specific names, such as Pacemaker Command Line Interface. Flaws listed only under those names are counted on their own pages, not here. If you run one of these, open its page for its own exploited flaws.
Which Pacemaker vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Pacemaker's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Pacemaker flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 3.3%CVE-2016-7797High
Pacemaker before 1.1.15, when using pacemaker remote, might allow remote attackers to cause a denial of service (node disconnection) via an unauthenticated connection.
- 3.0%CVE-2015-1867High
Pacemaker before 1.1.13 does not properly evaluate added nodes, which allows remote read-only users to gain privileges via an acl command.
- 2.6%CVE-2013-0281Medium
Pacemaker 1.1.10, when remote Cluster Information Base (CIB) configuration or resource management is enabled, does not limit the duration of connections to the blocking sockets, which allows remote attackers to cause...
- 1.9%CVE-2019-3885High
A 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 leaked via the system logs.
- 1.9%CVE-2020-25654High
An ACL bypass flaw was found in pacemaker.
- 0.5%CVE-2011-5271Medium
Pacemaker before 1.1.6 configure script creates temporary files insecurely
- 0.4%CVE-2018-16878Medium
A flaw was found in pacemaker up to and including version 2.0.1.
- 0.4%CVE-2016-7035High
An authorization flaw was found in Pacemaker before 1.1.16, where it did not properly guard its IPC interface.
- 0.4%CVE-2018-16877High
A flaw was found in the way pacemaker's client-server authentication was implemented in versions up to and including 2.0.0.
- 0.2%CVE-2010-2496Medium
stonith-ng in pacemaker and cluster-glue passed passwords as commandline parameters, making it possible for local attackers to gain access to passwords of the HA stack and potentially influence its operations.
Running Pacemaker? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
Pacemaker before 1.1.15, when using pacemaker remote, might allow remote attackers to cause a denial of service (node disconnection) via an unauthenticated connection.
- Matched to
- Pacemaker on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 10 published vulnerabilities listed under the name Pacemaker, across 50 versions.
None of Pacemaker's vulnerabilities is on the list of flaws known to be exploited today.
Clusterlabs also lists Pacemaker under more specific names, such as Pacemaker Command Line Interface. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.
Create a Precursor Intelligence account and track Pacemaker. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.