Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
25.10.4
-
None
-
MariaDB Cloud Staging
-
MXS-SPRINT-282
-
Can result in unexpected behaviour
-
Description
The Intelligent Proxy (exasolrouter) writes credentials to its logs in plain text. Anyone with access to the container/pod logs, or to any downstream log aggregation system, can read them. There are two distinct leak paths:
SQL statement text in SQLGlot warnings. When SQLGlot hits unsupported syntax and falls back to parsing as a Command, the full statement is logged, including the password literal in IDENTIFIED BY '...'.
ODBC connection strings in connection errors. When the router fails to connect a query handle, it logs the entire connection string, including the PWD= value (here, the service account credential used for the Exasol connection).
Evidence
Log excerpts (the credentials shown below are real and should be treated as compromised, see Notes):
2026-10-29T00:03:50.415594168Z stdout F 2026-10-29 00:03:50 warning: (266) [exasolrouter] (Exasol-Service); SQLGlot: 'CREATE USER rej_u IDENTIFIED BY '<password visible>'' contains unsupported syntax. Falling back to parsing as a 'Command'. |
 |
2026-10-29T16:52:57.64044726Z stdout F 2026-10-29 16:52:57 error : Could not connect query handle using 'DRIVER=/usr/lib64/maxscale/exasol/current/lib/libexaodbc.so;EXAHOST=compr-8daba3-exasol:8563;UID=skysql_maxscale_dbtgs37167356;PWD=<password visible>;FINGERPRINT=NOCERTCHECK;HOSTTIMEOUT=5000': [Exasol][Exasol Driver]No server listening. |
Steps to reproduce
Deploy Intelligent Proxy with the Exasol service configured in mariadb cloud.
Path 1: Run a statement SQLGlot cannot fully parse that contains a password, e.g. CREATE USER <user> IDENTIFIED BY '<password>'. Check the router log.
Path 2: Make the Exasol endpoint unreachable (or stop the service) and trigger a query that needs a new connection. Check the router log.
Expected behavior
Secrets are never written to logs at any log level. Passwords in SQL text are masked (e.g. IDENTIFIED BY '**'), and PWD= values in connection strings are redacted (e.g. PWD=**).
Actual behavior
Passwords appear in clear text in both the SQL fallback warning and the ODBC connection error.
Impact
Credential exposure to anyone with log access (operators, support, log aggregation/SIEM, shared support bundles).
Exposes both end-user passwords (from DDL such as CREATE USER / ALTER USER) and the internal service account used by the proxy.
Likely a compliance concern (SOC 2, PCI, GDPR secrets-handling requirements).
Attachments
Issue Links
- relates to
-
MXS-6890 A new variable, which can supress SQL-Statements in maxscale log
-
- Open
-