MariaDB Connector/Node.js: Possible SQL injection in Buffer parameter escaping under big5/gbk/sjis/cp932/gb18030 client charsets
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.4, 3.3.3, 3.4.6, and 3.5.3, MariaDB Connector/Node.js permits SQL injection when attacker-controlled Buffer parameters are escaped client-side under the big5, gbk, sjis, cp932, or gb18030 client character sets. PacketOutputStream.writeBufferEscape in lib/io/packet-output-stream.js escaped bytes without the charset-aware getMbRecognizer logic in lib/misc/charset-mb.js. The server SQL lexer runs my_ismbchar before escape processing, so an attacker-controlled lead byte can consume the inserted 0x5C backslash as a multibyte trail byte and leave the following 0x27 quote unescaped, terminating the string literal and allowing arbitrary SQL. The default utf8mb4 character set and parameters sent through the execute binary prepared-statement path are not affected. Successful exploitation can expose or modify data available to the database account. This issue is fixed in versions 3.2.4, 3.3.3, 3.4.6, and 3.5.3.
From the CVE record · GitHub_M
MariaDB Connector/Node.js can mishandle attacker-controlled Buffer parameters escaped client-side under the big5, gbk, sjis, cp932, or gb18030 character sets. An attacker who can supply such a parameter may inject SQL and expose or modify data accessible to the database account. The default utf8mb4 character set and the execute binary prepared-statement path are not affected.
Check Node.js applications using the npm mariadb package at versions below 3.2.4, 3.3.0 through 3.3.3, 3.4.0 through 3.4.5, or 3.5.0 through 3.5.2.