Clusterlabs Pacemaker

10 CVEs affecting Clusterlabs Pacemaker. Latest disclosed: 2021-10-18. Critical: 0, High: 4.

Top CVEs affecting Clusterlabs Pacemaker
CVESeverityScorePublishedSummary
CVE-2016-7035High8.82018-09-10An authorization flaw was found in Pacemaker before 1.1.16, where it did not properly guard its IPC interface. An attacker with an unprivileged account on a Pa…
CVE-2018-16877High7.82019-04-18A flaw was found in the way pacemaker's client-server authentication was implemented in versions up to and including 2.0.0. A local attacker could use this fla…
CVE-2016-7797High7.52017-03-24Pacemaker before 1.1.15, when using pacemaker remote, might allow remote attackers to cause a denial of service (node disconnection) via an unauthenticated con…
CVE-2020-25654High7.22020-11-24An 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…
CVE-2010-2496Medium5.52021-10-18stonith-ng in pacemaker and cluster-glue passed passwords as commandline parameters, making it possible for local attackers to gain access to passwords of the…
CVE-2011-5271Medium5.52019-11-12Pacemaker before 1.1.6 configure script creates temporary files insecurely
CVE-2018-16878Medium5.52019-04-18A flaw was found in pacemaker up to and including version 2.0.1. An insufficient verification inflicted preference of uncontrolled processes can lead to DoS
CVE-2019-3885Low3.32019-04-18A 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…
CVE-2015-18672015-08-12Pacemaker before 1.1.13 does not properly evaluate added nodes, which allows remote read-only users to gain privileges via an acl command.
CVE-2013-02812013-11-23Pacemaker 1.1.10, when remote Cluster Information Base (CIB) configuration or resource management is enabled, does not limit the duration of connections to the…