Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven

CVE-2023-45859

HIGH

CVE-2023-45859 is a high-severity (CVSS 7.6) CWE-922 vulnerability in com.hazelcast:hazelcast. O3 Security confirms whether CVE-2023-45859 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Missing permission checks on Hazelcast client protocol

Also known asGHSA-xh6m-7cr7-xx66
Published
Feb 28, 2024
Updated
Jul 15, 2026
Affected
8 pkgs
Patched
2 / 8
Exploits
None indexed

Blast Radius

8 pkgs affected
com.hazelcast:hazelcastcom.hazelcast:hazelcastcom.hazelcast:hazelcastcom.hazelcast:hazelcastcom.hazelcast:hazelcastcom.hazelcast:hazelcastcom.hazelcast:hazelcast-allcom.hazelcast:hazelcast-all

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

In Hazelcast through 4.1.10, 4.2 through 4.2.8, 5.0 through 5.0.5, 5.1 through 5.1.7, 5.2 through 5.2.4, and 5.3 through 5.3.2, some client operations don't check permissions properly, allowing authenticated users to access data stored in the cluster.

Affected Packages

8 total 2 fixed
EcosystemPackageVulnerable rangeFix
Mavencom.hazelcast:hazelcastall versionsNo fix
Mavencom.hazelcast:hazelcast4.2No fix
Mavencom.hazelcast:hazelcast5.0No fix
Mavencom.hazelcast:hazelcast5.1No fix
Mavencom.hazelcast:hazelcast5.2.0&&< 5.2.55.2.5
Mavencom.hazelcast:hazelcast5.3.0&&< 5.3.55.3.5

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.hazelcast:hazelcast. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    No patched version of com.hazelcast:hazelcast has shipped for CVE-2023-45859 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether CVE-2023-45859 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2023-45859. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

In Hazelcast through 4.1.10, 4.2 through 4.2.8, 5.0 through 5.0.5, 5.1 through 5.1.7, 5.2 through 5.2.4, and 5.3 through 5.3.2, some client operations don't check permissions properly, allowing authenticated users to access data stored in the cluster.
O3 Security · Impact-Aware SCA

Is CVE-2023-45859 in your dependencies?

O3 detects CVE-2023-45859 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.