MariaDB Connector/J denial of service in OK packet 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, when CLIENT_SESSION_TRACK was negotiated, the OkPacket.parse() and OkPacket.parseWithInfo() paths allocated byte arrays using server-declared lengths for the OK packet info field and session-state variable names and values before confirming that the bytes remained in the packet. A malicious or compromised server, or a machine-in-the-middle attacker, could send a small OK packet declaring a much larger length and repeatedly force attacker-controlled heap allocations before the subsequent copy failed. This could create garbage-collection pressure or an OutOfMemoryError in the client application. This issue is fixed in versions 3.3.7, 3.4.5, and 3.5.11.
From the CVE record · GitHub_M
When CLIENT_SESSION_TRACK is negotiated, MariaDB Connector/J allocates memory based on server-declared OK packet lengths before checking that the packet contains the declared bytes. A malicious or compromised server, or a machine-in-the-middle attacker, can send crafted packets that cause garbage-collection pressure or an OutOfMemoryError in the client application.
Teams using Maven package org.mariadb.jdbc:mariadb-java-client in versions >=3.0.0 <3.3.7, >=3.4.0 <3.4.5, or >=3.5.0 <3.5.11 should check their deployments.