MariaDB Connector/J: LOAD DATA LOCAL INFILE file check could be satisfied by text inside quoted identifiers, letting a malicious server read client files
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in org.mariadb.jdbc:mariadb-java-client 3.3.7, org.mariadb.jdbc:mariadb-java-client 3.4.5 and org.mariadb.jdbc:mariadb-java-client 3.5.11.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| MariaDB | >=3.0.0 <3.3.7, >=3.4.0 <3.4.5, >=3.5.0 <3.5.11 | ||
| maven: org.mariadb.jdbc:mariadb-java-client | >=3.0.0 <3.3.7, >=3.4.0 <3.4.5, >=3.5.0 <3.5.11 | 3.3.7, 3.4.5, 3.5.11 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in org.mariadb.jdbc:mariadb-java-client (Maven), strongest first
Embed
A live severity badge for an advisory, README or ticket