Skip to content
Fencer Intel
medium 4.3

CVE-2023-33264 json

Hazelcast vulnerable to unmasked password exposure

published 3y ago modified 4mo ago also GHSA-5gj6-62g7-vmgf , EUVD-2023-1474

cvss
4.3
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 54%
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, configuration routines don't mask passwords in the member configuration properly. This allows Hazelcast Management Center users to view some of the secrets.

Patch / fix

  • maven com.hazelcast:hazelcast 5.0.5, 5.1.6, 5.2.4, 5.3.0
  • hazelcast hazelcast 5.1.6

Is CVE-2023-33264 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

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2023-33264 updated cvss 4.3

hazelcast: Improper password mask

  • Red Hat Fuse 7 hazelcast hazelcast Red Hat Integration Camel Quarkus 2 hazelcast hazelcast
    affected: no fix planned “Will not fix”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

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

CVSS scores

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

Affected packages

ecosystem package affected fixed in
maven com.hazelcast:hazelcast
>=4.0-BETA-1, <=4.2.8
>=5.0-BETA-1, <5.0.5
>=5.1-BETA-1, <5.1.6
>=5.2-BETA-1, <5.2.4
>=5.3.0-BETA-1, <5.3.0
5.0.5
5.1.6
5.2.4
5.3.0

Classification

Weakness
  • CWE-522 Insufficiently Protected Credentials
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

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.