cassandra-jdbc-wrapper: Authentication Token Exposed in Logs
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in com.ing.data:cassandra-jdbc-wrapper 4.16.4 and com.ing.data:cassandra-jdbc-wrapper 5.0.2.
cassandra-jdbc-wrapper provides a JDBC-compliant API over the Java driver for Apache Cassandra. Prior to 4.16.4 and 5.0.2, DriverUtil.toStringWithoutSensitiveValues() and DriverUtil.redactSensitiveValuesInJdbcUrl() redact the password property but not the equally sensitive token property used for DataStax Astra and other token-based authentication. When DEBUG logging is enabled, SessionHolder passes connection properties and JDBC URLs containing token through these helpers, causing the live token to be written in plaintext when connections are acquired or released. An attacker who can read those logs can use the token to access Cassandra data and operations authorized to that credential. This issue is fixed in versions 4.16.4 and 5.0.2.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| ing-bank | <4.16.4, >=5.0.0 <5.0.2 | ||
| maven: com.ing.data:cassandra-jdbc-wrapper | <=4.16.3, >=5.0.0 <5.0.2 | 4.16.4, 5.0.2 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket