GitHub Advisoryadvisory · Maven
GHSA-xh6m-7cr7-xx66 Missing permission checks on Hazelcast client protocol
HIGH
Official page ↗
- Aliases
- CVE-2023-45859
- Ecosystem
- Maven
- Packages
- com.hazelcast:hazelcast, com.hazelcast:hazelcast-all
- Severity
- High
- CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L
- Weaknesses
- CWE-281, CWE-922
- Reviewed
- 2024-02-27
Affected packages
• Maven com.hazelcast:hazelcast: <= 4.1.10 (no fix yet)
• Maven com.hazelcast:hazelcast: >= 4.2, <= 4.2.8 (no fix yet)
• Maven com.hazelcast:hazelcast: >= 5.0, <= 5.0.5 (no fix yet)
• Maven com.hazelcast:hazelcast: >= 5.1, <= 5.1.7 (no fix yet)
• Maven com.hazelcast:hazelcast: >= 5.2.0, < 5.2.5 → fixed in 5.2.5
• Maven com.hazelcast:hazelcast: >= 5.3.0, < 5.3.5 → fixed in 5.3.5
• Maven com.hazelcast:hazelcast-all: <= 4.1.10 (no fix yet)
• Maven com.hazelcast:hazelcast-all: >= 4.2, <= 4.2.8 (no fix yet)
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.
Related
Alias · CVE (1)
- CVE-2023-45859 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… vulnerability