Skip to content

Missing permission checks on Hazelcast client protocol

High severity GitHub Reviewed Published Feb 27, 2024 in hazelcast/hazelcast • Updated May 30, 2025

Package

maven com.hazelcast:hazelcast (Maven)

Affected versions

<= 4.1.10
>= 4.2, <= 4.2.8
>= 5.0, <= 5.0.5
>= 5.1, <= 5.1.7
>= 5.2.0, <= 5.2.4
>= 5.3.0, < 5.3.5

Patched versions

5.2.5
5.3.5
maven com.hazelcast:hazelcast-all (Maven)
<= 4.1.10
>= 4.2, <= 4.2.8
None

Description

Impact

In Hazelcast through 4.1.10, 4.2 through 4.2.8, 5.0 through 5.0.5, 5.1 through 5.1.7, 5.2 through 5.2.4, and 5.3 through 5.3.2, some client operations don't check permissions properly, allowing authenticated users to access data stored in the cluster.

Patches

Fix versions: 5.2.5, 5.3.5, 5.4.0-BETA-1

Workarounds

There is no known workaround.

References

@kwart kwart published to hazelcast/hazelcast Feb 27, 2024
Published to the GitHub Advisory Database Feb 27, 2024
Reviewed Feb 27, 2024
Published by the National Vulnerability Database Feb 28, 2024
Last updated May 30, 2025

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
Low

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:L/UI:N/S:U/C:H/I:L/A:L

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(37th percentile)

Weaknesses

CVE ID

CVE-2023-45859

GHSA ID

GHSA-xh6m-7cr7-xx66

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.