CyberSecBulletin
CVE-2022-2735NVD status: Modified

ClusterLabs/pcs: Incorrect Default Permissions

CVE-2022-2735 is a high-severity incorrect default permissions vulnerability in ClusterLabs/pcs, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. Affected ClusterLabs/pcs versions: Affects v0.10.5 and later including all 0.11.x.. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.32% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Check which version of ClusterLabs/pcs you run against the affected versions below, and install the vendor's latest release.

Affected products and versions

VendorProductAffected versionsFixed in
ClusterLabs/pcsClusterLabs/pcsAffects v0.10.5 and later including all 0.11.x.Not stated
ClusterlabsPcs0.10.5 through 0.11.3Not stated
DebianDebian Linux11.0Not stated

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
LocalThe attacker needs local access or must trick a user into running something.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.

Official description

A vulnerability was found in the PCS project. This issue occurs due to incorrect permissions on a Unix socket used for internal communication between PCS daemons. A privilege escalation could happen by obtaining an authentication token for a hacluster user. With the "hacluster" token, this flaw allows an attacker to have complete control over the cluster managed by PCS.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Incorrect Default Permissions

During installation, installed file permissions are set to allow anyone to modify those files.

How developers prevent this class of flaw

  • The architecture needs to access and modification attributes for files to only those users who actually require those actions.
  • Compartmentalize the system to have safe areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

More Incorrect Default Permissions vulnerabilities (CWE-276)

Timeline

  1. CVE record published.
  2. Record last changed materially (score, affected products, status or references).

References

Patches and release notes

Third-party and government advisories

Other vulnerabilities in ClusterLabs/pcs

All ClusterLabs/pcs vulnerabilities

Recent Incorrect Default Permissions vulnerabilities

Spotted an error? Tell us.