dbcve.org
Sensitive Information in LogsWeakness · CWE-532

CVE-2025-0736

MEDIUM · 5.5 CVSS v3.1 Published 2025-01-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A flaw was found in Infinispan, when using JGroups with JDBC_PING. This issue occurs when an application inadvertently exposes sensitive information, such as configuration details or credentials, through logging mechanisms. This exposure can lead to unauthorized access and exploitation by malicious actors.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Infinispan with JGroups JDBC_PING incorrectly logs sensitive information such as configuration details or credentials through the application's logging mechanisms. This exposes sensitive data that could be harvested by malicious actors with access to logs, leading to potential unauthorized access.

MitigationReview and configure logging to filter or mask sensitive data in JGroups JDBC_PING connections, ensuring credentials and configuration details are not written to logs. Implement proper log sanitization or disable verbose logging for sensitive components.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify JGroups JDBC_PING protocol is in use
    Check your Infinispan or JGroups configuration files (typically jgroups.xml or infinispan.xml) for the <JDBC_PING> element or protocol configuration. Also check for any JDBC_PING-related class names in the cluster configuration.
    Affected if JDBC_PING protocol is configured as the discovery mechanism for the cluster
  2. Locate Infinispan and JGroups configuration files
    Search for configuration files containing JDBC_PING: commonly named jgroups.xml, cluster.xml, infinispan.xml, or custom XML files in the application config directory. Also check for -Djgroups.conf or similar JVM arguments pointing to config files.
    Affected if JDBC_PING configuration is found in any configuration file
  3. Inspect JDBC_PING connection configuration for sensitive data
    Open the JDBC_PING configuration and examine the connection-url, username, password, and any other connection properties. Check if credentials appear in plain text within the XML or properties configuration.
    Affected if Database credentials or connection strings are present in JDBC_PING configuration in plain text
  4. Review application and JGroups logs for sensitive data leakage
    Search log files (application logs, jgroups logs, container logs) for patterns matching JDBC_PING, database connection strings, or credentials. Use grep or similar to search for 'jdbc', 'ping', 'password', 'username' within cluster-related log entries.
    Affected if Log files contain JDBC_PING connection details, database URLs, usernames, or passwords in plain text
  5. Check log level configuration for JGroups and JDBC components
    Examine logging configuration (logback.xml, log4j.xml, or similar) for the JGroups and JDBC_PING related loggers. Check if DEBUG, TRACE, or VERBOSE logging is enabled for org.jgroups.protocols.JDBC_PING or related packages.
    Affected if DEBUG, TRACE, or verbose logging is enabled for JDBC_PING or JGroups discovery protocols

A user is affected if their Infinispan deployment uses JGroups JDBC_PING for cluster discovery and sensitive credentials or connection details are written to logs without sanitization.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Review and configure logging to filter or mask sensitive data in JGroups JDBC_PING connections, ensuring credentials and configuration details are not written to logs. Implement proper log sanitization or disable verbose logging for sensitive components.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,304.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-0736 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-0736 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data