NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
LOW severity

CVE-2023-5384 — infinispan-core

LOWFix: infinispan/infinispan#11555

CVE-2023-5384 is a low-severity (CVSS 2.7) CWE-312 vulnerability in org.infinispan:infinispan-core. A fix is available for org.infinispan:infinispan-core — see the affected versions and patch details below.

Infinispan caches credentials in clear text

Published
Updated
Affected
16 pkgs
Patched
16 / 16
Exploits
None indexed
Exploitation data as of Nov 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • A successful exploit gives an attacker total control of the affected component, not partial access.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2023-5384.

EPSS Exploitation Probability

via FIRST.org ↗
0.5%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs46th percentile — riskier than 46% of all scored CVEsHighest risk
0.04%0.38%0.71%1.05%0.5%0.5%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

16 pkgs affected
☕org.infinispan:infinispan-core☕org.infinispan:infinispan-core☕org.infinispan:infinispan-commons☕org.infinispan:infinispan-commons☕org.infinispan:infinispan-hotrod☕org.infinispan:infinispan-hotrod☕org.infinispan:infinispan-client-hotrod☕org.infinispan:infinispan-client-hotrod+8 more

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

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.

Affected Packages

16 total 16 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.infinispan:infinispan-core≥ 15.0.0.Dev01&&< 15.0.0.Dev0715.0.0.Dev07org.infinispan:infinispan-core:15.0.0.Dev07
☕Mavenorg.infinispan:infinispan-coreall versions14.0.25.Finalorg.infinispan:infinispan-core:14.0.25.Final
☕Mavenorg.infinispan:infinispan-commons≥ 15.0.0.Dev01&&< 15.0.0.Dev0715.0.0.Dev07org.infinispan:infinispan-commons:15.0.0.Dev07
☕Mavenorg.infinispan:infinispan-commonsall versions14.0.25.Finalorg.infinispan:infinispan-commons:14.0.25.Final
☕Mavenorg.infinispan:infinispan-hotrod≥ 15.0.0.Dev01&&< 15.0.0.Dev0715.0.0.Dev07org.infinispan:infinispan-hotrod:15.0.0.Dev07
☕Mavenorg.infinispan:infinispan-hotrodall versions14.0.25.Finalorg.infinispan:infinispan-hotrod:14.0.25.Final

Affected Products

3 products · 3 configurations
Application
infinispaninfinispan
all
Application
data gridredhat
< 8.4.6
range
Application
jboss data gridredhat
all

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.infinispan:infinispan-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.infinispan:infinispan-core to 15.0.0.Dev07 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-5384 is resolved across your whole dependency graph.

  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.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

Red Hat evaluated this vulnerability and this only affects Infinispan's server component, so Red Hat JBoss Enterprise Application Platform (EAP) and other tools that may run infinispan is not affected.

Workaround published by Red Hat
The issue's impact is limited because only users with administrator permissions can retrieve the cache configurations, and the recommended approach for connecting via JDBC is using the `datasource` configuration, which does not expose the database credentials.
Source: Red Hat security advisory for CVE-2023-5384 (CC BY 4.0)
ProductFixed inAdvisory
Red Hat Data Grid 8.4.6infinispanRHSA-2023:7676

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is CVE-2023-5384 in your dependencies?

Find it across Maven, including transitive dependencies.

CVE-2023-5384: infinispan-core — Fixed in 15.0.0.Dev07