GHSA-GRFQ-R75J-RW9X
MariaDB Connector/J: Server could switch character_set_results away from UTF-8 without the client noticing
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| 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-GRFQ-R75J-RW9X divulgada | |
| Divulgación | Modificada | Última actualización del registro | |
| Monitoreo | Detectada | Ingresó al índice |
Summary
MariaDB Connector/J decodes every result as UTF-8 and guards
`character_set_client` against a change to another charset, but did not guard
`character_set_results`, and relied on the server's global
`session_track_system_variables` list to be told about charset changes at all.
Details
The connector learns about session variable changes through session tracking,
and closes the connection when `character_set_client` is switched away from UTF-8,
so that its UTF-8 decoding stays correct. Two gaps remained:
- `character_set_results` was not guarded: a server could switch it to another
- the list of tracked variables came from the server's global
The fix requests an explicit session tracking list that includes both character
set variables whatever the server's global setting, and closes the connection
when `character_set_results` is changed to a charset other than `utf8`, `utf8mb3`
or `utf8mb4`, as it already did for `character_set_client`.
Impact
Integrity: a malicious or compromised server, or a MitM, can make the strings an
application reads differ from the bytes the server returned (inappropriate
encoding for the output context), which can defeat application-side validation
or escaping built on those values. Exploitation requires control of the server
side of the connection; no confidentiality or availability impact.
Credit
Reported by fg0x0
Incluye detalles técnicos publicados por el investigador. Úselos solo para validar y corregir sus propios sistemas.
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde 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 |
3.3.73.4.53.5.11Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://nvd.nist.gov/vuln/detail/CVE-2026-119281https://github.com/mariadb-corporation/mariadb-connector-j/security/advisories/GHSA-grfq-r75j-rw9xhttps://github.com/mariadb-corporation/mariadb-connector-j/commit/af5e565eb171cfc66ea8e948ddc616abed0c4623https://github.com/mariadb-corporation/mariadb-connector-j/commit/d51b968c1b795c73d24e0b3f960205b7bc82d423https://github.com/mariadb-corporation/mariadb-connector-j/commit/fdabe74a7df6dce1d6c099f4d0ca1e2acc25919ahttps://github.com/mariadb-corporation/mariadb-connector-jhttps://github.com/mariadb-corporation/mariadb-connector-j/releases/tag/3.3.7https://github.com/mariadb-corporation/mariadb-connector-j/releases/tag/3.4.5https://github.com/mariadb-corporation/mariadb-connector-j/releases/tag/3.5.11Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
