CVE-2023-5384 | Infinispan: credentials returned from configuration as clear text

A flaw was found in Infinispan. When serializing the configuration for a cache to XML/JSON/YAML, which contains credentials (JDBC store with connection pooling, remote store), the credentials are returned in clear text as part of the configuration.

Published: 2023-12-18 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2023-5384 is rated Moderate Risk (52.7/100): CVSS High severity, with medium exploitation likelihood (EPSS 0.55%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2023-5384

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-04-28 0.41% 0.55% +0.13%
2 2026-04-18 0.53% 0.41% -0.11%
3 2026-03-04 — 0.53% —

Full EPSS history (18 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2023-5384

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.2 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:H)
They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.2 5.9 [email protected]
2.7 3.1 LOW
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:H)
They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 1.2 1.4 [email protected]

Weakness enumeration for CVE-2023-5384

GitHub Security Advisory for CVE-2023-5384

GHSA-gg57-587f-h5v6 · Severity: medium · Ecosystem: maven — Infinispan caches credentials in clear text

OS Trackers for CVE-2023-5384

vendor priority summary link
redhat high — https://access.redhat.com/security/cve/CVE-2023-5384

Affected software / configurations for CVE-2023-5384

Vendor Product Version Raw CPE
redhat data_grid < 8.4.6 cpe:2.3:a:redhat:data_grid:*:*:*:*:*:*:*:*
redhat jboss_data_grid — cpe:2.3:a:redhat:jboss_data_grid:-:*:*:*:text-only:*:*:*
infinispan infinispan — cpe:2.3:a:infinispan:infinispan:-:*:*:*:*:*:*:*

References for CVE-2023-5384

cvelogic Threat Intelligence