MariaDB Connector/J denial of service in XA RECOVER parsing
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. From 3.0.0 until 3.3.7, 3.4.5, and 3.5.11, the MariaDbPoolConnection.recover() and MariaDbPoolPinnedConnection.recover() implementations trusted the gtrid_length and bqual_length columns returned by XA RECOVER. The methods allocated and split Xid byte arrays without validating the lengths against Xid.MAXGTRIDSIZE, Xid.MAXBQUALSIZE, or the actual data payload. A malicious or compromised server, or a machine-in-the-middle attacker, could cause large allocations, NegativeArraySizeException, or ArrayIndexOutOfBoundsException during XA recovery. This issue is fixed in versions 3.3.7, 3.4.5, and 3.5.11.
From the CVE record · GitHub_M
MariaDB Connector/J does not validate lengths returned by XA RECOVER before allocating and splitting Xid byte arrays. During XA recovery, a malicious or compromised server, or a machine-in-the-middle attacker, can cause large allocations or exceptions. The input does not specify authentication or user-interaction requirements.
Check applications using Maven package org.mariadb.jdbc:mariadb-java-client versions >=3.0.0 <3.3.7, >=3.4.0 <3.4.5, or >=3.5.0 <3.5.11.