Your RSA-2048 keys break in 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
Dec 28, 2023
Updated
Sep 10, 2026
Affected
16 pkgs
Patched
16 / 16
Exploits
None indexed
Exploitation data as of Sep 21, 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 CVEs44th percentile — riskier than 44% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

CVE-2023-5384 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 377,636 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

16 pkgs affected
org.infinispan:infinispan-coreorg.infinispan:infinispan-coreorg.infinispan:infinispan-commonsorg.infinispan:infinispan-commonsorg.infinispan:infinispan-hotrodorg.infinispan:infinispan-hotrodorg.infinispan:infinispan-client-hotrodorg.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-core15.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-commons15.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-hotrod15.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

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.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2023-5384 can be triaged on real exposure rather than presence alone.

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

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.

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?

O3 Security finds CVE-2023-5384 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

CVE-2023-5384: infinispan-core (Low 2.7) | O3 Security