Skip to content
Fencer Intel
high 8.8

CVE-2023-33265 json

Hazelcast Executor Services don't check client permissions properly

published 3y ago modified 4mo ago also GHSA-c5vj-wp4v-mmvx , EUVD-2023-2023

cvss
8.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.7%
EPSS 0.7% chance of exploitation in 30 days, percentile 53%
public exploits
0
none known

Summary

In Hazelcast through 5.0.4, 5.1 through 5.1.6, and 5.2 through 5.2.3, executor services don't check client permissions properly, allowing authenticated users to execute tasks on members without the required permissions granted.

Patch / fix

  • maven com.hazelcast:hazelcast 5.0.5, 5.1.7, 5.2.4
  • maven com.hazelcast:hazelcast-enterprise 5.0.5, 5.1.7, 5.2.4
  • hazelcast hazelcast 5.0.5, 5.1.7, 5.2.4

Is CVE-2023-33265 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
2y ago

Exploit prediction

0.69% chance of exploitation in the next 30 days, higher than 53% of all scored CVEs (FIRST EPSS, 2026-11-15).

CVSS scores

assigned by version score vector
NVD 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
GitHub 3.1 7.6 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:H

Affected packages

ecosystem package affected fixed in
maven com.hazelcast:hazelcast
>=5.2.0, <5.2.4
>=5.1.0, <5.1.7
<5.0.5
5.2.4
5.1.7
5.0.5
maven com.hazelcast:hazelcast-enterprise
>=5.2.0, <5.2.4
>=5.1.0, <5.1.7
<5.0.5
5.2.4
5.1.7
5.0.5

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.