MariaDB Connector/J: Server could switch character_set_results away from UTF-8 without the client noticing
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_resultswas not guarded: a server could switch it to another charset, after which the bytes of every result were decoded as UTF-8 although encoded otherwise.- the list of tracked variables came from the server's global
session_track_system_variables: a server configured, or made, not to track the character set variables could change them silently.
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
Czego dotyczy
Kliknij technologię, aby zobaczyć wszystkie dotyczące jej podatności.
| Platforma | Paczka | Podatne wersje | Poprawka w wersji |
|---|---|---|---|
| Java / Kotlin (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 |
Odnośniki
- https://github.com/mariadb-corporation/mariadb-connector-j/security/advisories/GHSA-grfq-r75j-rw9x
- https://nvd.nist.gov/vuln/detail/CVE-2026-119281
- https://github.com/mariadb-corporation/mariadb-connector-j/commit/af5e565eb171cfc66ea8e948ddc616abed0c4623
- https://github.com/mariadb-corporation/mariadb-connector-j/commit/d51b968c1b795c73d24e0b3f960205b7bc82d423
- https://github.com/mariadb-corporation/mariadb-connector-j/commit/fdabe74a7df6dce1d6c099f4d0ca1e2acc25919a
- https://github.com/mariadb-corporation/mariadb-connector-j
- https://github.com/mariadb-corporation/mariadb-connector-j/releases/tag/3.3.7
- https://github.com/mariadb-corporation/mariadb-connector-j/releases/tag/3.4.5
- https://github.com/mariadb-corporation/mariadb-connector-j/releases/tag/3.5.11
- Wektor CVSS
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N- Słabość (CWE)
CWE-838- Platforma
- Java / Kotlin (Maven)
- Paczka
org.mariadb.jdbc:mariadb-java-client- Ujawniono
- 30.10.2026
- Aktualizacja
- 31.10.2026 01:17
Źródła i licencje
OSV / GitHub Advisory Database - GHSA-grfq-r75j-rw9x - CC BY 4.0
Historia podatności: org.mariadb.jdbc:mariadb-java-client
Wszystkie opisane podatności tej paczki (Java / Kotlin (Maven)), od najnowszej. Widać, czy to jednorazowa wpadka, czy paczka, której trzeba pilnować.
- Wszystkich wpisów
- 9
- Pierwsza → ostatnia
- 08.2026 10.2026
- Bez poprawki
- 0
- Wykorzystywana w atakach
- 0
Rozkład istotności
- Średnia 7
- Niska 2
Ujawnienia w latach
- 2026: 9
-
MariaDB Connector/J: Server could switch character_set_results away from UTF-8 without the client noticing ten wpis
Dowiedz się, które podatności dotyczą Twojej aplikacji
Po podłączeniu integracji DockRay i włączeniu raportowania oprogramowania DockRay porównuje zgłoszone wersje komponentów ze znanymi podatnościami i powiadamia o potwierdzonych dopasowaniach. Zakres zależy od obsługiwanej technologii i dostępnych biuletynów.