PT-2026-117327 · Hazelcast Technologies+1 · Hazelcast+1
CVSS v4.0
10
Critical
| Vector | AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
Name of the Vulnerable Software and Affected Versions
Apache Camel versions 4.0.0 through 4.18.4
Apache Camel versions 4.19.0 through 4.22.0
Description
The
camel-hazelcast component fails to apply a JavaSerializationFilterConfig to Hazelcast instances created through specific configuration paths. This occurs when ReplicatedHazelcastAggregationRepository overrides the doStart() function without calling the super method, and when HazelcastDefaultComponent#getOrCreateHzClientInstance() builds a ClientConfig while hazelcastMode is set to client without a referenced ClientConfig or hazelcastConfigUri. Consequently, Java deserialization remains unrestricted. An attacker capable of publishing data to the connected Hazelcast cluster can trigger the deserialization of a crafted Java object within the serialization layer, leading to remote code execution. This risk is heightened as Hazelcast clusters do not enable authentication or TLS by default.Recommendations
Upgrade to version 4.18.5 for the 4.18.x releases stream.
Upgrade to version 4.22.1 for the 4.22.x releases stream.
Upgrade to version 4.23.0.
Supply an explicit Hazelcast configuration containing a
JavaSerializationFilterConfig or inject a pre-built HazelcastInstance.
Set the JVM-wide filter -Djdk.serialFilter=!java.net.;java.;javax.;org.apache.camel.;!*.
Enable Hazelcast cluster authentication and TLS.Fix
RCE
Deserialization of Untrusted Data
Found an issue in the description? Have something to add? Feel free to write us 👾
Weakness Enumeration
Related Identifiers
Affected Products
Apache Camel
Hazelcast