GHSA-H599-M3W5-9M7X
MariaDB Connector/J: Rogue server can drive large heap allocations from server-declared lengths in OK packets
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Remediación | Parche 3.3.7 | org.mariadb.jdbc:mariadb-java-client · -9 d desde divulgación | |
| Remediación | Parche 3.4.5 | org.mariadb.jdbc:mariadb-java-client · -9 d desde divulgación | |
| Remediación | Parche 3.5.11 | org.mariadb.jdbc:mariadb-java-client · -9 d desde divulgación | |
| Divulgación | Publicada | GHSA-H599-M3W5-9M7X divulgada | |
| Divulgación | Modificada | Última actualización del registro | |
| Monitoreo | Detectada | Ingresó al índice |
Summary
MariaDB Connector/J sized heap allocations from lengths declared by the server
in OK packets before checking that those lengths fit in the packet. A rogue or
MitM server can make the client allocate megabytes from a packet of a few bytes.
Details
When `CLIENT_SESSION_TRACK` is negotiated (the default), an OK packet carries an
info field followed by session-state blocks, each tracked variable being sent as a
length-encoded name and value. `OkPacket.parse()` and `parseWithInfo()` allocated
`new byte[len]` for the info field, the variable name and the value with the
server-declared `len`, then copied the packet data into it. The copy failed with an
`ArrayIndexOutOfBoundsException` when the packet was shorter, but only after the
allocation had taken place.
A server-declared length of 8 MiB in an 18-byte packet was enough to trigger an
8 MiB allocation; the integer-range validation of length-encoded values does not
help, since such lengths are valid positive integers.
The fix validates every server-declared length against the remaining packet bytes
before any allocation (`ReadableByteBuf.checkLength()` and a bounded
`readBytes(int)`), and stops reading the session state at the first inconsistent
entry.
Impact
Availability only: a malicious or compromised server, or a MitM, can drive
attacker-controlled heap allocations on every OK packet, creating GC pressure up to
`OutOfMemoryError` in the client application. Exploitation requires control of the
server side of the connection; no authentication bypass, confidentiality or
integrity impact.
Credit
Reported by fg0x0
Incluye detalles técnicos publicados por el investigador. Úselos solo para validar y corregir sus propios sistemas.
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
mavenorg.mariadb.jdbc:mariadb-java-client |
Corregida | 3.3.7, 3.4.5, 3.5.11 | -9 d · -9 d · -9 d | 4.0.0 no afectada |
3.3.73.4.53.5.11Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://nvd.nist.gov/vuln/detail/CVE-2026-119276https://github.com/mariadb-corporation/mariadb-connector-j/security/advisories/GHSA-h599-m3w5-9m7xhttps://github.com/mariadb-corporation/mariadb-connector-j/commit/b9e1ee8d9b4d820d70719504cdfd5c97f1aede5fhttps://github.com/mariadb-corporation/mariadb-connector-j/commit/beb445fcf9294113878fc05ac77f0efdf0596ac6https://github.com/mariadb-corporation/mariadb-connector-j/commit/ea8c7b6537e50053444188a9a3fd9cae99550f56https://github.com/mariadb-corporation/mariadb-connector-jhttps://github.com/mariadb-corporation/mariadb-connector-j/releases/tag/3.3.7https://github.com/mariadb-corporation/mariadb-connector-j/releases/tag/3.4.5https://github.com/mariadb-corporation/mariadb-connector-j/releases/tag/3.5.11Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
