Uploaded image for project: 'MariaDB MaxScale'
  1. MariaDB MaxScale
  2. MXS-7708

maxscale logs expose connection string password in plaintext

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 25.10.4
    • 26.10.1
    • exasolrouter
    • None
    • MariaDB Cloud Staging
    • MXS-SPRINT-282
    • Can result in unexpected behaviour
    • Hide
      The Exasol router could write passwords to the MaxScale log: the error logged when connecting to Exasol failed included the ODBC connection string, and the warnings of SQLGlot quoted the statement, including any password in it. The connection string is no longer logged in the error messages, and the output of SQLGlot and the preprocessor is now logged only at info level. Note that with log_info enabled, MaxScale logs complete SQL statements, including any passwords they contain.
      Show
      The Exasol router could write passwords to the MaxScale log: the error logged when connecting to Exasol failed included the ODBC connection string, and the warnings of SQLGlot quoted the statement, including any password in it. The connection string is no longer logged in the error messages, and the output of SQLGlot and the preprocessor is now logged only at info level. Note that with log_info enabled, MaxScale logs complete SQL statements, including any passwords they contain.

    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

          Activity

            People

              johan.wikman Johan Wikman
              allen.herrera Allen Herrera
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - 2d
                  2d
                  Remaining:
                  Remaining Estimate - 0d
                  0d
                  Logged:
                  Time Spent - 0.25d Time Not Required
                  0.25d

                  Git Integration

                    Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.