com.hazelcast:hazelcast vulnerabilities
Core Hazelcast Module
- Registry
- Maven
- Latest
- 5.7.0
- License
- The Apache Software License, Version 2.0
10 known advisories
The latest version, 5.7.0, is not affected by any of them. Projects on older versions may be.
mvn versions:use-dep-version -Dincludes=com.hazelcast:hazelcast -DdepVersion=5.7.0 -DforceVersion=trueIs your project on an affected com.hazelcast:hazelcast?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for com.hazelcast:hazelcast
Hazelcast allows arbitrary member memory access by low-privileged client
- Affected
- >=5.6.0 <5.7.0 · >=5.5.0 <5.7.0 · <5.7.0
- Fixed in
- 5.7.0
Hazelcast has an authorization bypass in IMap Predicates API
- Affected
- >=5.6.0 <5.7.0 · >=5.5.0 <5.7.0 · <5.7.0
- Fixed in
- 5.7.0
Missing permission checks on Hazelcast client protocol
- Affected
- <=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
- Fixed in
- 5.2.5, 5.3.5
Hazelcast Platform permission checking in CSV File Source connector
- Affected
- >=5.3.0 <5.3.5 · >=5.2.0 <5.2.5 · <=5.1.7
- Fixed in
- 5.2.5, 5.3.5
Hazelcast Executor Services don't check client permissions properly
- Affected
- >=5.2.0 <5.2.4 · >=5.1.0 <5.1.7 · <5.0.5
- Fixed in
- 5.0.5, 5.1.7, 5.2.4
Hazelcast vulnerable to unmasked password exposure
- Affected
- >=4.0-BETA-1 <=4.2.8 · >=5.0-BETA-1 <5.0.5 · >=5.1-BETA-1 <5.1.6 · >=5.2-BETA-1 <5.2.4 · >=5.3.0-BETA-1 <5.3.0
- Fixed in
- 5.0.5, 5.1.6, 5.2.4, 5.3.0
Hazelcast connection caching
- Affected
- <3.12.13 · >=4.0 <=4.0.6 · >=4.1 <4.1.10 · >=4.2 <4.2.6 · >=5.0 <5.0.4 · >=5.1 <5.1.3
- Fixed in
- 3.12.13, 4.1.10, 4.2.6, 5.0.4, 5.1.3
Deserialization of Untrusted Data in Hazelcast
- Affected
- <3.11
- Fixed in
- 3.11
XML External Entity Reference in Hazelcast
- Affected
- >=5.1-beta1 <5.1
- Fixed in
- 5.1
Security Advisory for "Log4Shell"
- Affected
- >=5.0 <5.0.2 · >=4.0.0 <4.0.5 · >=4.1.1 <4.1.8 · >=4.2 <4.2.4
- Fixed in
- 4.0.5, 4.1.8, 4.2.4, 5.0.2
Is your com.hazelcast:hazelcast version vulnerable?
- com.hazelcast:hazelcast 5.7No known advisories in 5.7.0
- com.hazelcast:hazelcast 5.62 advisories in 5.6.0
- com.hazelcast:hazelcast 5.52 advisories in 5.5.0
- com.hazelcast:hazelcast 5.42 advisories in 5.4.0
- com.hazelcast:hazelcast 5.32 advisories in 5.3.8
- com.hazelcast:hazelcast 5.22 advisories in 5.2.5
- com.hazelcast:hazelcast 4.26 advisories in 4.2.8
- com.hazelcast:hazelcast 4.16 advisories in 4.1.10
- com.hazelcast:hazelcast 4.07 advisories in 4.0.6
- com.hazelcast:hazelcast 3.125 advisories in 3.12.13
- com.hazelcast:hazelcast 3.116 advisories in 3.11.7
- com.hazelcast:hazelcast 3.107 advisories in 3.10.7
- com.hazelcast:hazelcast 3.97 advisories in 3.9.4
- com.hazelcast:hazelcast 3.87 advisories in 3.8.9
- com.hazelcast:hazelcast 3.77 advisories in 3.7.8
Which of your client projects still run an old com.hazelcast:hazelcast?
NPMscan reads the pom.xml, build.gradle and gradle.lockfile in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other Maven packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Maven registry.