Skip to content

Insufficient authorization validation between zones when xCAT zones are enabled

High
besawn published GHSA-hpxg-7428-6jvv Mar 8, 2023

Package

xCAT-server

Affected versions

< 2.16.5

Patched versions

2.16.5

Description

The xCAT zones feature can be used to divide groups of nodes in the cluster into multiple zones that have independent ssh keys. xCAT zones are optional and not enabled by default. If zones are configured in xCAT, it is possible for a root user from one node to obtain ssh keys from other zones and SSH to any node in any zone, breaking the zone enforcement.

Impact

Only users that use the optional zones feature are impacted. All versions of xCAT prior to xCAT 2.16.5 are vulnerable.

Patches

The issue has been fixed in xCAT 2.16.5. Users making use of zones should upgrade to xCAT 2.16.5.

Workarounds

The problem can be worked around by disabling zones or patching the management node with the fix contained in #7247.

Acknowledgement

We would like to thank Dr. Stefan Albensoeder (Enercon) for reporting this issue, as well as contributing to the fix.

References

#7246
#7247

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

CVE ID

CVE-2023-27486

Weaknesses

No CWEs

Credits