MariaDB Connector/J: Inappropriate Encoding for Output Context in org.mariadb.jdbc:mariadb-java-client
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. Prior to 2.7.14, 3.3.5, 3.4.3, and 3.5.9, the connector encodes and decodes protocol text and performs client-side escaping under the assumption that the connection character set is UTF-8. The server can report a mid-session change to character_set_client through OK-packet session-state tracking, including a change caused by SET NAMES, a stored routine or trigger, server configuration, or a hostile server. If character_set_client changes to a non-UTF-8 value, the driver continues to read and write UTF-8 while the server interprets the same bytes under another encoding, causing silent data corruption and a client/server charset-confusion mismatch that can defeat byte-wise quoting or escaping. The fix accepts only utf8, utf8mb3, or utf8mb4 after initialization; any other value causes SQLException with SQLState 08000 and closes the connection. This issue is fixed in versions 2.7.14, 3.3.5, 3.4.3, and 3.5.9.
From the CVE record · GitHub_M
MariaDB Connector/J assumes the connection character set remains UTF-8 after initialization. If the server reports a mid-session change to a non-UTF-8 character set, the mismatch can silently corrupt data or defeat byte-wise quoting and escaping. This can occur through configuration, SQL operations, or a hostile server; the input does not specify authentication or user-interaction requirements.
Teams using Maven package org.mariadb.jdbc:mariadb-java-client in versions before 2.7.14, 3.0.0 through 3.3.4, 3.4.0 through 3.4.2, or 3.5.0 through 3.5.8 should check their deployments.