Vulnerability in com.hazelcast:hazelcast (CVE-2022-36437)
Summary
Vulnerability in com.hazelcast:hazelcast (CVE-2022-36437). Confidential information can be exposed externally. Mitigation: upgrade to 5.1.3 or later.
Original description
The description as published by the source.
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.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2022-36437 has been found in com.hazelcast:hazelcast.
Confidential information can be exposed externally.
What to do: upgrade com.hazelcast:hazelcast to 5.1.3 or later.
If unsure, ask your IT team or search "com.hazelcast:hazelcast CVE-2022-36437" on the vendor's site.
CVE-2022-36437 (com.hazelcast:hazelcast) — CWE-384
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 5.1.3 — apply immediately
Workaround: There is no known workaround, but setups with TLS and mutual authentication enabled significantly lowers the exploitation risk.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-384) exists in com.hazelcast:hazelcast.
Check the vendor advisory for the affected versions of com.hazelcast:hazelcast.
Severity: ?. Confidential information can be exposed externally.
Update to 5.1.3.
Workaround: There is no known workaround, but setups with TLS and mutual authentication enabled significantly lowers the exploitation risk.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで com.hazelcast:hazelcast を使っているサービスとバージョンを洗い出す。
-
2Apply temporary workaround mitigate
There is no known workaround, but setups with TLS and mutual authentication enabled significantly lowers the exploitation risk.パッチが適用されるまでの応急処置として、There is no known workaround, but setups with TLS and mutual authentication enabled significantly lowers the exploitation risk. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade com.hazelcast:hazelcast to 5.1.3ステージング環境で 5.1.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web support.hazelcast.com