MariaDB Connector/Node.js: SQL injection in the text protocol when the session uses NO_BACKSLASH_ESCAPES
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 3.2.5, 3.3.4, 3.4.7, and 3.5.4, text-protocol escaping always prefixes quotes with a backslash and does not honor the session's NO_BACKSLASH_ESCAPES mode, including in Connection.escape(). When that mode is enabled, the backslash is an ordinary character, so an attacker-controlled placeholder value can close the SQL string literal and inject arbitrary SQL with the application's database privileges. The vulnerable configuration may be enabled server-wide, through connector initialization options, or with an application-issued SET sql_mode; execute() and batch() use binary protocols and are not affected. This issue is fixed in versions 3.2.5, 3.3.4, 3.4.7, and 3.5.4.
From the CVE record · GitHub_M
MariaDB Connector/Node.js does not honor NO_BACKSLASH_ESCAPES when escaping values for the text protocol, including in Connection.escape(). If that mode is enabled, an attacker who can control a placeholder value can inject SQL that runs with the application's database privileges. execute() and batch() use binary protocols and are not affected.
Teams using the npm mariadb package should check versions below 3.2.5, 3.3.0 through 3.3.3, 3.4.0 through 3.4.6, and 3.5.0-rc.0 through versions below 3.5.4.