CVE-2023-45859 json
Missing permission checks on Hazelcast client protocol
published 2024-02-27 2 y ago modified 2026-07-08 4 mo ago also GHSA-xh6m-7cr7-xx66 , EUVD-2024-0767
- cvss
- 7.6
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 44%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- maven com.hazelcast:hazelcast 5.2.5, 5.3.5
- hazelcast hazelcast 5.2.5, 5.3.5
- github.com/hazelcast/hazelcast#25509 pull request
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
0.52% chance of exploitation in the next 30 days, higher than 44% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 7.6 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L |
| CNA | 3.1 | 7.6 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L |
| GitHub | 3.1 | 7.6 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | com.hazelcast:hazelcast | <=4.1.10 >=4.2, <=4.2.8 >=5.0, <=5.0.5 >=5.1, <=5.1.7 >=5.2.0, <5.2.5 >=5.3.0, <5.3.5 |
5.2.5 5.3.5 |
| maven | com.hazelcast:hazelcast-all | <=4.1.10 >=4.2, <=4.2.8 |
no fix listed |
Classification
References
-
github.com
/hazelcast/hazelcast/pull/25509
web, patch
-
github.com
/hazelcast/hazelcast/security/advisories/GHSA-xh6m-7cr7-xx66
web, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2023-45859
advisory
-
github.com
/hazelcast/hazelcast
package
Sources
- CVE List CVE-2023-45859
- GitHub Advisory GHSA-xh6m-7cr7-xx66
- NVD CVE-2023-45859
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.