MariaDB Connector/R2DBC: Inappropriate Encoding for Output Context and Improper Encoding or Escaping of Output in org.mariadb:r2dbc-mariadb
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| mariadb-corporation | mariadb-connector-r2dbc | affected |
|
||||||
| org.mariadb | r2dbc-mariadb | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Mariadb-corporation | Mariadb-connector-r2dbc |
|
||||||||
| Org.mariadb | R2dbc-mariadb |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-5rqc-86vf-g8r2 | org.mariadb:r2dbc-mariadb has Inappropriate Encoding for Output Context and Improper Encoding or Escaping of Output |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.486% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Mariadb-corporation
Mariadb-corporation mariadb-connector-r2dbc Org.mariadb Org.mariadb r2dbc-mariadb |
|
| Vendors & Products |
Mariadb-corporation
Mariadb-corporation mariadb-connector-r2dbc Org.mariadb Org.mariadb r2dbc-mariadb |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | MariaDB Connector/R2DBC is a non-blocking MariaDB and MySQL client implemented in Java. Prior to 1.4.1, org.mariadb:r2dbc-mariadb encodes and decodes all character data under the assumption that the connection character set is UTF-8. A server can announce a mid-session change to character_set_client through the OK-packet session-state-tracking mechanism, including through SET NAMES executed by a stored routine or trigger, server configuration, or a hostile or man-in-the-middle server. If the new character set is not UTF-8, the driver continues to exchange UTF-8 while the server interprets the same bytes under a different 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 raises R2dbcNonTransientResourceException with SQLState 08000 and closes the connection. This issue is fixed in version 1.4.1. | |
| Title | MariaDB Connector/R2DBC: Inappropriate Encoding for Output Context and Improper Encoding or Escaping of Output in org.mariadb:r2dbc-mariadb | |
| Weaknesses | CWE-116 CWE-838 |
|
| References |
|
|
| Metrics |
cvssV3_1
|