MariaDB Connector/Node.js: Connector leaks the cleartext password to an MitM despite `ssl: true`
mariadb-corporation mariadb-connector-nodejs
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| mariadb npm |
|
|
mariadb-corporation mariadb-connector-nodejs
| Product | Affected | Fixed in |
|---|---|---|
| mariadb npm |
|
|
MariaDB Connector/Node.js is used to connect applications developed on Node.js to MariaDB and MySQL databases. Prior to versions 3.3.3, 3.4.6, and 3.5.3, when ssl is enabled without a pinned CA or server certificate, MariaDB Connector/Node.js sends credentials before completing certificate fingerprint validation. In lib/cmd/handshake/auth/handshake.js, a server that selects mysql_clear_password as the initial authentication plugin can receive the password before the post-TLS identity check. In lib/cmd/handshake/authentication.js, an authentication switch can evaluate the previous plugin instead of the requested target plugin, allowing mysql_clear_password to send the credential first. An active man-in-the-middle can present a self-signed certificate, capture the database password, and use it to authenticate directly even though the connector later rejects the server and closes the connection. This issue is fixed in versions 3.3.3, 3.4.6, and 3.5.3.
From the CVE record · GitHub_M
When SSL is enabled without a pinned CA or server certificate, MariaDB Connector/Node.js can send a database password before completing certificate identity validation. An active man-in-the-middle can capture the password using a self-signed certificate, even though the connector later rejects the server.
Check applications using the npm mariadb package at versions below 3.2.4, 3.3.0 through 3.3.2, 3.4.0 through 3.4.5, or 3.5.0 through 3.5.2.