MariaDB Connector/Node.js: SQL injection through object keys in SET expansion (permitSetMultiParamEntries)
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. From 3.2.0 until 3.2.5, 3.3.4, 3.4.7, and 3.5.4, applications that enable permitSetMultiParamEntries can pass objects whose keys are expanded into a SQL SET clause without being processed by escapeId. An attacker-controlled key containing a backtick can close the quoted identifier and cause the remainder of the key to be interpreted as SQL. This can update columns the application did not intend to expose and can append arbitrary SQL with the database user's privileges. The option is disabled by default, and serialized-object handling used when it is disabled is 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 escape object keys expanded into SQL SET clauses when permitSetMultiParamEntries is enabled. If an attacker can control a key, a backtick can turn it into SQL that updates unintended columns or runs arbitrary SQL with the database user's privileges. The option is disabled by default, and serialized-object handling when it is disabled is not affected.
Check applications using the npm mariadb package in versions >=3.2.0 <3.2.5, >=3.3.0 <3.3.4, >=3.4.0 <3.4.7, or >=3.5.0-rc.0 <3.5.4.