MariaDB Connector/J: Length-encoded integers larger than Integer.MAX_VALUE were truncated before being used as lengths
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 3.3.7, 3.4.5, 3.5.10
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
MariaDB Connector/J, the Java client library used to connect applications to MariaDB and MySQL databases, is affected. A malicious or compromised database server, or an attacker intercepting the connection, could cause the client to crash with errors or consume excessive memory during connection handling.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
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.10, the ReadableByteBuf.readLength() and ReadableByteBuf.readIntLengthEncodedNotNull() methods narrowed the protocol's unsigned 8-byte length-encoded integer to a Java int without checking that the value fit a non-negative integer. Values above Integer.MAX_VALUE could wrap to a negative or unrelated length that downstream allocation and read paths used. A malicious or compromised server, or a machine-in-the-middle attacker, could trigger NegativeArraySizeException, out-of-bounds failures, or oversized allocation behavior in client connection handling. This issue is fixed in versions 3.3.7, 3.4.5, and 3.5.10.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- mariadb-corporation mariadb-connector-j
From 3.0.0 · fixed in 3.3.7; From 3.4.0 · fixed in 3.4.5; From 3.5.0 · fixed in 3.5.10