dbcve.org
HazelcastApplication

CVE-2022-36437

CRITICAL · 9.1 CVSS v3.1 Published 2022-12-29
Fix available
A fix is available. Upgrade to 3.12.13 / 4.1.10 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The Connection handler in Hazelcast and Hazelcast Jet allows a remote unauthenticated attacker to access and manipulate data in the cluster with the identity of another already authenticated connection. The affected Hazelcast versions are through 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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is a critical authentication bypass vulnerability in Hazelcast's connection handler where a remote unauthenticated attacker can impersonate an already authenticated connection, allowing unauthorized access and manipulation of cluster data. The vulnerability enables complete identity spoofing without any credentials.

MitigationUpgrade Hazelcast to version 5.1.3 or later (5.0.4+, 4.2.6+, 4.1.10+, 4.0.7+), and Hazelcast Jet to 4.5.4 or later. Review access logs for indicators of compromise and consider credential rotation as a precaution.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
HazelcastApplication
Affected:< 3.12.13>= 4.0.0, < 4.1.10>= 4.2.0, < 4.2.6>= 5.0.0, < 5.0.4>= 5.1.0, < 5.1.3
Hazelcast JetApplication
Affected:< 4.5.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Hazelcast product and version
    Check the JAR file name in the deployment directory, or inspect the MANIFEST.MF file inside the hazelcast jar, or run: java -cp hazelcast-*.jar com.hazelcast.core.Server --version
    Affected if The version shown is lower than 3.12.13, or between 4.0.0-4.1.9, 4.2.0-4.2.5, 5.0.0-5.0.3, or 5.1.0-5.1.2 (for Hazelcast) or lower than 4.5.4 (for Hazelcast Jet)
  2. Confirm Hazelcast Jet vs Hazelcast
    Determine whether the deployed product is Hazelcast or Hazelcast Jet by checking the product name in the JAR or configuration files
    Affected if The product is Hazelcast Jet and the version is below 4.5.4
  3. Check network binding configuration
    Inspect the hazelcast.xml or hazelcast.yaml configuration file for the <network> section, specifically look for the <join> element and check if <interfaces> is configured or if the instance binds to non-localhost addresses
    Affected if The cluster is bound to 0.0.0.0 or a public IP address rather than localhost only, making it network-accessible
  4. Verify member-to-member authentication
    Check the <security> section in the Hazelcast configuration for member authentication settings, and review whether TLS/SSL is enabled for inter-member communication
    Affected if No member authentication or TLS is configured for cluster member connections

You are affected if Hazelcast or Hazelcast Jet is running a version that falls within any of the affected ranges AND the cluster is network-accessible to untrusted sources.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.12.13 / 4.1.10 / 4.2.6 or later
Fixed in 3.12.134.1.104.2.6
Interim mitigation

Upgrade Hazelcast to version 5.1.3 or later (5.0.4+, 4.2.6+, 4.1.10+, 4.0.7+), and Hazelcast Jet to 4.5.4 or later. Review access logs for indicators of compromise and consider credential rotation as a precaution.

Recommended fix High confidence

Hazelcast: 3.12.13+ (3.x), 4.1.10+ (4.0.x), 4.2.6+ (4.2.x), 5.0.4+ (5.0.x) | Hazelcast Jet: 4.5.4+

  1. 1. Identify your current Hazelcast or Hazelcast Jet version by checking your dependency management system or running cluster info
  2. 2. Determine which major version line you are on (3.x, 4.x, or 5.x)
  3. 3. For Hazelcast 3.x users: upgrade to version 3.12.13 or later
  4. 4. For Hazelcast 4.0.x users: upgrade to version 4.1.10 or later (consider jumping to 4.2.6+ or 5.0.4+ for longer support)
  5. 5. For Hazelcast 4.2.x users: upgrade to version 4.2.6 or later (consider jumping to 5.0.4+ for longer support)
  6. 6. For Hazelcast 5.0.x users: upgrade to version 5.0.4 or later
  7. 7. For Hazelcast Jet users: upgrade to version 4.5.4 or later
  8. 8. Update your Maven/Gradle dependency version accordingly
Caveat Review Hazelcast migration guides when upgrading across major versions; ensure client compatibility with new server version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Hazelcast Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-36437 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-36437 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data