MariaDB Connector/J file-name validation bypass in LOAD DATA LOCAL INFILE
mariadb-corporation mariadb-connector-j
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.mariadb.jdbc:mariadb-java-client Maven |
|
|
mariadb-corporation mariadb-connector-j
| Product | Affected | Fixed in |
|---|---|---|
| org.mariadb.jdbc:mariadb-java-client Maven |
|
|
MariaDB Connector/J is used to connect applications developed in Java to MariaDB and MySQL databases. From 3.0.0 until 3.3.7, 3.4.5, and 3.5.11, the ClientMessage.validateLocalFileName() check used a regular expression that could match LOAD DATA LOCAL INFILE text inside quoted identifiers, string literals, or comments instead of requiring a real statement. A malicious or compromised server, or a machine-in-the-middle attacker, could return crafted database or table identifiers that the connector reused in metadata or updatable-result queries, then answer with a LOCAL INFILE request for a client file. With allowLocalInfile enabled, this caused the connector to stream any readable client-host file named by the crafted text, including through DatabaseMetaData.getImportedKeys(), DatabaseMetaData.getExportedKeys(), or ResultSet.updateRow() paths. This issue is fixed in versions 3.3.7, 3.4.5, and 3.5.11.
From the CVE record · GitHub_M
MariaDB Connector/J can mistake LOAD DATA LOCAL INFILE text inside quoted identifiers, strings, or comments for a real statement. A malicious or compromised server, or a machine-in-the-middle attacker, can use crafted identifiers and a LOCAL INFILE request to read a client-host file when allowLocalInfile is enabled.
Teams using Maven package org.mariadb.jdbc:mariadb-java-client in versions >=3.0.0 <3.3.7, >=3.4.0 <3.4.5, or >=3.5.0 <3.5.11 should check their deployments.