DEV Community

CVE Reports
CVE Reports

Posted on Originally published at cvereports.com

CVE-2026-73504: CVE-2026-73504: Plaintext Authentication Token Exposure in cassandra-jdbc-wrapper Debug Logs

CVE-2026-73504: Plaintext Authentication Token Exposure in cassandra-jdbc-wrapper Debug Logs

Vulnerability ID: CVE-2026-73504
CVSS Score: 5.5
Published: 2026-11-19

CVE-2026-73504 (GHSA-jc42-994r-vvwp) is a credential exposure vulnerability in ING Bank's cassandra-jdbc-wrapper (com.ing.data:cassandra-jdbc-wrapper). Resulting from an incomplete remediation of AIKIDO-2024-10565, the log sanitization routines in DriverUtil redact the password property but fail to redact the token property. When DEBUG logging is enabled, connection properties and JDBC URLs containing DataStax Astra DB bearer tokens are written in plaintext to application logs, enabling local users or log aggregation readers to harvest active database credentials.

TL;DR

An incomplete log redaction routine in cassandra-jdbc-wrapper versions prior to 4.16.4 and 5.0.2 writes plaintext authentication tokens (such as DataStax Astra DB tokens) to application logs when DEBUG logging is active.


Technical Details

  • CVE / Advisory ID: CVE-2026-73504 / GHSA-jc42-994r-vvwp
  • Weakness Class: CWE-532 (Insertion of Sensitive Information into Log File)
  • CVSS v3.1 Score: 5.5 Medium (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N)
  • Attack Vector: Local / Log File & SIEM Read Access
  • Affected Package: com.ing.data:cassandra-jdbc-wrapper (< 4.16.4, 5.0.0 - 5.0.1)
  • Patched Versions: 4.16.4 and 5.0.2
  • Exploit / KEV Status: No known public exploits; Not listed in CISA KEV

Affected Systems

  • com.ing.data:cassandra-jdbc-wrapper (Maven / Java)
  • cassandra-jdbc-wrapper (4.x Branch): < 4.16.4 (Fixed in: 4.16.4)
  • cassandra-jdbc-wrapper (5.x Branch): >= 5.0.0, < 5.0.2 (Fixed in: 5.0.2)

Code Analysis

Commit: ace58f7

Redact sensitive token property in DriverUtil (5.x / master branch)

--- a/src/main/java/com/ing/data/cassandra/jdbc/utils/DriverUtil.java
+++ b/src/main/java/com/ing/data/cassandra/jdbc/utils/DriverUtil.java
@@ -54,6 +54,7 @@ import java.util.stream.Collectors;

 import static com.ing.data.cassandra.jdbc.utils.JdbcUrlUtil.TAG_PASSWORD;
+import static com.ing.data.cassandra.jdbc.utils.JdbcUrlUtil.TAG_TOKEN;
 import static com.ing.data.cassandra.jdbc.utils.WarningConstants.DRIVER_PROPERTY_NOT_FOUND;
 import static com.ing.data.cassandra.jdbc.utils.WarningConstants.URL_REDACTION_FAILED;
 import static org.apache.commons.collections4.ListUtils.emptyIfNull;
@@ -315,6 +316,9 @@ public static String toStringWithoutSensitiveValues(final Properties properties)
         if (withRedactedSensitiveValues.containsKey(TAG_PASSWORD)) {
             withRedactedSensitiveValues.setProperty(TAG_PASSWORD, "***");
         }
+        if (withRedactedSensitiveValues.containsKey(TAG_TOKEN)) {
+            withRedactedSensitiveValues.setProperty(TAG_TOKEN, "***");
+        }
         return withRedactedSensitiveValues.toString();
     }

@@ -341,6 +345,9 @@ public static String redactSensitiveValuesInJdbcUrl(final String jdbcUrl) {
                     if (param.startsWith(TAG_PASSWORD + "=")) {
                         return TAG_PASSWORD + "=***";
                     }
+                    if (param.startsWith(TAG_TOKEN + "=")) {
+                        return TAG_TOKEN + "=***";
+                    }
                     return param;
                 })
                 .collect(Collectors.joining("&"));
Enter fullscreen mode Exit fullscreen mode

Commit: 0b7ea03

Backport token property redaction in DriverUtil to 4.x branch

--- a/src/main/java/com/ing/data/cassandra/jdbc/utils/DriverUtil.java
+++ b/src/main/java/com/ing/data/cassandra/jdbc/utils/DriverUtil.java
@@ -54,6 +54,7 @@ import java.util.stream.Collectors;

 import static com.ing.data.cassandra.jdbc.utils.JdbcUrlUtil.TAG_PASSWORD;
+import static com.ing.data.cassandra.jdbc.utils.JdbcUrlUtil.TAG_TOKEN;
 import static com.ing.data.cassandra.jdbc.utils.WarningConstants.DRIVER_PROPERTY_NOT_FOUND;
 import static com.ing.data.cassandra.jdbc.utils.WarningConstants.URL_REDACTION_FAILED;
 import static org.apache.commons.collections4.ListUtils.emptyIfNull;
@@ -315,6 +316,9 @@ public static String toStringWithoutSensitiveValues(final Properties properties)
         if (withRedactedSensitiveValues.containsKey(TAG_PASSWORD)) {
             withRedactedSensitiveValues.setProperty(TAG_PASSWORD, "***");
         }
+        if (withRedactedSensitiveValues.containsKey(TAG_TOKEN)) {
+            withRedactedSensitiveValues.setProperty(TAG_TOKEN, "***");
+        }
         return withRedactedSensitiveValues.toString();
     }

@@ -341,6 +345,9 @@ public static String redactSensitiveValuesInJdbcUrl(final String jdbcUrl) {
                     if (param.startsWith(TAG_PASSWORD + "=")) {
                         return TAG_PASSWORD + "=***";
                     }
+                    if (param.startsWith(TAG_TOKEN + "=")) {
+                        return TAG_TOKEN + "=***";
+                    }
                     return param;
                 })
                 .collect(Collectors.joining("&"));
Enter fullscreen mode Exit fullscreen mode

Mitigation Strategies

  • Upgrade cassandra-jdbc-wrapper to a patched release (4.16.4+ or 5.0.2+).
  • Pass sensitive authentication parameters (token, password) via java.util.Properties rather than raw JDBC URL query strings.
  • Restrict logger verbosity for the com.ing.data.cassandra.jdbc namespace to INFO or WARN.
  • Rotate all DataStax Astra DB tokens and database credentials that may have been logged during DEBUG sessions.
  • Apply regex-based log scrubbing in log shipping and SIEM ingestion pipelines.

Remediation Steps:

  1. Update com.ing.data:cassandra-jdbc-wrapper to version 4.16.4 (for 4.x users) or 5.0.2 (for 5.x users) in your build configuration.
  2. Verify that logback.xml or log4j2.xml configurations set com.ing.data.cassandra.jdbc to INFO or higher in production and staging environments.
  3. Search existing application log files and centralized log indices for instances of 'AstraCS:' or 'token='.
  4. Revoke and regenerate any exposed authentication tokens via the DataStax Astra console and purge affected log segments.

References


Read the full report for CVE-2026-73504 on our website for more details including interactive diagrams and full exploit analysis.

Top comments (0)