MariaDB Connector/J: Server could switch character_set_results away from UTF-8 without the client noticing
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 connector assumed result bytes were UTF-8 but guarded only changes to character_set_client. It did not reject non-UTF-8 character_set_results changes and relied on the server's global session_track_system_variables configuration to report character-set changes. A malicious or compromised server, or a machine-in-the-middle attacker, could suppress tracking or change the result charset so application strings differed from the returned bytes, potentially defeating application-side validation or escaping that depended on the decoded values. 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