llamaCVEVulnerability Intelligence
/
Advisory · GitHub · Maven · org.mariadb.jdbc:mariadb-java-client

GHSA-FHX5-2XQW-2CGM

MariaDB Connector/J: LOAD DATA LOCAL INFILE file check could be satisfied by text inside quoted identifiers, letting a malicious server read client files

Parche disponible
Descargar PNG JSON
CVSS
—
medium
Fuente: —
ExplotaciónSin evidenciaNo figura en CISA KEV
Exploits públicos0Ninguno conocido
Parche3 versionesPrimer parche a -9 d de la divulgación
Exposición20 dDesde la divulgación, 30 oct 2026, 5:59 p. m.
Detección17 dDesde la divulgación hasta su ingreso al índice
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada +1
Explotación
Remediación
Parche 3.3.7 +2
Monitoreo
Detectada
21 oct 26
30 oct 26
17 nov 26
20 nov 26
21 oct 26
29 oct 26
5 nov 26
13 nov 26
20 nov 26
FechaFaseEventoDetalle
Remediación Parche 3.3.7 org.mariadb.jdbc:mariadb-java-client · -9 d desde divulgación
Remediación Parche 3.4.5 org.mariadb.jdbc:mariadb-java-client · -9 d desde divulgación
Remediación Parche 3.5.11 org.mariadb.jdbc:mariadb-java-client · -9 d desde divulgación
Divulgación Publicada GHSA-FHX5-2XQW-2CGM divulgada
Divulgación Modificada Última actualización del registro
Monitoreo Detectada Ingresó al índice
Resumen
Descripción del advisory
Texto original · GitHub · en inglés

Summary

MariaDB Connector/J checked a server's LOAD DATA LOCAL INFILE file request by
searching the text of the command it had sent for
`LOAD DATA LOCAL INFILE '<file>'`. The search also matched inside quoted
identifiers, string literals and comments, so text returned by the server and
re-used in a later query could satisfy it. A rogue or MitM server can read any
file the client JVM can read.

Details

When a server answers a command with a LOCAL INFILE request (`0xFB` packet), the
connector opens the named file on the client host and streams it to the server,
after verifying that the file corresponds to a `LOAD DATA LOCAL INFILE` of the
command it sent (`ClientMessage.validateLocalFileName()`). That verification was a
regular expression whose prefix accepted any character, so it answered "does the
text appear anywhere in the SQL", including inside a backtick-quoted identifier.

Several driver paths put identifiers returned by the server straight back into
their next query: `DatabaseMetaData.getImportedKeys()` and `getExportedKeys()`
re-use database and table names from `SHOW DATABASES`, `SHOW TABLES` and the
`REFERENCES` clause of `SHOW CREATE TABLE` output, and updatable result sets build
their `UPDATE` and refresh `SELECT` from the schema and table names of the column
definition packets. A server returning an identifier such as
``LOAD DATA LOCAL INFILE '/etc/passwd'`` makes the connector send
``SHOW CREATE TABLE `LOAD DATA LOCAL INFILE '/etc/passwd'`.`accounts` ``; the
server answers it with a LOCAL INFILE request for `/etc/passwd`, the check
passes, and the file content is sent. On the `getImportedKeys()` path the
resulting error is swallowed and the application observes nothing. The same
applies to an application that interpolates identifiers obtained from the
server into its own queries.

The fix parses the command instead of searching it: string literals, quoted
identifiers and comments are skipped, statements are split on `;`, and only a
`LOAD DATA|XML [LOW_PRIORITY|CONCURRENT] LOCAL INFILE` found at the start of a
statement is considered, its file literal or bound parameter being compared
exactly to the requested file.

Impact

Confidentiality: a malicious or compromised server, or a MitM, can read arbitrary
files from the host running the JDBC client (application configuration,
credential files, key stores, ...) through standard `java.sql` calls such as
`DatabaseMetaData.getImportedKeys()`, `getExportedKeys()` or
`ResultSet.updateRow()`. Exploitation requires control of the server side of the
connection and `allowLocalInfile` enabled (the default). Setting
`allowLocalInfile=false` is a workaround when LOAD DATA LOCAL INFILE is not
needed. No integrity or availability impact.

Credit

Reported by buxuwa (buxu) through HackerOne

Incluye detalles técnicos publicados por el investigador. Úselos solo para validar y corregir sus propios sistemas.

Versiones

Rangos afectados

Afectada Corregida Última
org.mariadb.jdbc:mariadb-java-client≥ 3.0.0 < 3.3.7
org.mariadb.jdbc:mariadb-java-client≥ 3.4.0 < 3.4.5
org.mariadb.jdbc:mariadb-java-client≥ 3.5.0 < 3.5.11
3.0.0
3.3.7
3.4.0
3.4.5
3.5.0
3.5.11
4.0.0
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
mavenorg.mariadb.jdbc:mariadb-java-client
Corregida 3.3.7, 3.4.5, 3.5.11 -9 d · -9 d · -9 d 4.0.0 no afectada
Versiones corregidas3.3.73.4.53.5.11
Explotación

Arsenal público

Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.

Referencias
Advisoryhttps://nvd.nist.gov/vuln/detail/CVE-2026-119210
Otrahttps://github.com/mariadb-corporation/mariadb-connector-j/security/advisories/GHSA-fhx5-2xqw-2cgm
Otrahttps://github.com/mariadb-corporation/mariadb-connector-j/commit/4d2f8002399949ed7f138e9c0b75b69229538120
Otrahttps://github.com/mariadb-corporation/mariadb-connector-j/commit/5812e0ca7574c3934915179b76f2e819a556d099
Otrahttps://github.com/mariadb-corporation/mariadb-connector-j/commit/a4891f877f1c885a573194771c1ed0aacec0ce1d
Otrahttps://github.com/mariadb-corporation/mariadb-connector-j
Otrahttps://github.com/mariadb-corporation/mariadb-connector-j/releases/tag/3.3.7
Otrahttps://github.com/mariadb-corporation/mariadb-connector-j/releases/tag/3.4.5
Otrahttps://github.com/mariadb-corporation/mariadb-connector-j/releases/tag/3.5.11

Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.