CVE-2023-45859GHSA-XH6M-7CR7-XX66
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
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.2.5, 5.3.5
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: partial
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- n/a n/a
Version range not reported
- com.hazelcast:hazelcastMaven
through 4.1.10
- com.hazelcast:hazelcastMaven
From 4.2 · through 4.2.8
- com.hazelcast:hazelcastMaven
From 5.0 · through 5.0.5
- com.hazelcast:hazelcastMaven
From 5.1 · through 5.1.7
- com.hazelcast:hazelcastMaven
From 5.2.0 · fixed in 5.2.5
- com.hazelcast:hazelcastMaven
From 5.3.0 · fixed in 5.3.5
- com.hazelcast:hazelcast-allMaven
through 4.1.10
- com.hazelcast:hazelcast-allMaven
From 4.2 · through 4.2.8