GHSA-c5hg-mr8r-f6jp Hazelcast connection caching

• Maven com.hazelcast:hazelcast: < 3.12.13 → fixed in 3.12.13 • Maven com.hazelcast:hazelcast: >= 4.0, <= 4.0.6 (no fix yet) • Maven com.hazelcast:hazelcast: >= 4.1, < 4.1.10 → fixed in 4.1.10 • Maven com.hazelcast:hazelcast: >= 4.2, < 4.2.6 → fixed in 4.2.6 • Maven com.hazelcast:hazelcast: >= 5.0, < 5.0.4 → fixed in 5.0.4 • Maven com.hazelcast:hazelcast: >= 5.1, < 5.1.3 → fixed in 5.1.3 • Maven com.hazelcast.jet:hazelcast-jet: < 4.5.4 → fixed in 4.5.4 • Maven com.hazelcast.jet:hazelcast-jet-enterprise: < 4.5.4 → fixed in 4.5.4 • Maven com.hazelcast:hazelcast-enterprise: < 3.12.13 → fixed in 3.12.13 • Maven com.hazelcast:hazelcast-enterprise: >= 4.0, <= 4.0.6 (no fix yet) • Maven com.hazelcast:hazelcast-enterprise: >= 4.1, < 4.1.10 → fixed in 4.1.10 • Maven com.hazelcast:hazelcast-enterprise: >= 4.2, < 4.2.6 → fixed in 4.2.6 • Maven com.hazelcast:hazelcast-enterprise: >= 5.0, < 5.0.4 → fixed in 5.0.4 • Maven com.hazelcast:hazelcast-enterprise: >= 5.1, < 5.1.3 → fixed in 5.1.3

Impact The Connection handler in Hazelcast and Hazelcast Jet allows an unauthenticated, remote attacker to access and manipulate data in the cluster with another authenticated connection's identity. The affected Hazelcast versions are through 3.12.12, 4.0.6, 4.1.9, 4.2.5, 5.0.3, and 5.1.2. The affected Hazelcast Jet versions are through 4.5.3. Patches Hazelcast Jet (and Enterprise) 4.5.4. Hazelcast IMDG (and Enterprise)3.12.13 Hazelcast IMDG (and Enterprise) 4.1.10 Hazelcast IMDG (and Enterprise) 4.2.6 Hazelcast Platform (and Enterprise) 5.1.3 Workarounds There is no known workaround, but setups with TLS and mutual authentication enabled significantly lowers the exploitation risk. References https://support.hazelcast.com/s/article/Security-Advisory-for-CVE-2022-36437