org.mariadb.jdbc:mariadb-java-client vulnerabilities
JDBC driver for MariaDB and MySQL
- Registry
- Maven
- Latest
- 4.0.0
- License
- LGPL-2.1-or-later
9 known advisories
The latest version, 4.0.0, is not affected by any of them. Projects on older versions may be.
mvn versions:use-dep-version -Dincludes=org.mariadb.jdbc:mariadb-java-client -DdepVersion=4.0.0 -DforceVersion=trueIs your project on an affected org.mariadb.jdbc:mariadb-java-client?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for org.mariadb.jdbc:mariadb-java-client
MariaDB Connector/J: Rogue server can drive large heap allocations from server-declared lengths in OK packets
- Affected
- >=3.0.0 <3.3.7 · >=3.4.0 <3.4.5 · >=3.5.0 <3.5.11
- Fixed in
- 3.3.7, 3.4.5, 3.5.11
MariaDB Connector/J: Length-encoded integers larger than Integer.MAX_VALUE were truncated before being used as lengths
- Affected
- >=3.0.0 <3.3.7 · >=3.4.0 <3.4.5 · >=3.5.0 <3.5.10
- Fixed in
- 3.3.7, 3.4.5, 3.5.10
MariaDB Connector/J: XA recover() trusted server-supplied gtrid and bqual lengths
- Affected
- >=3.0.0 <3.3.7 · >=3.4.0 <3.4.5 · >=3.5.0 <3.5.11
- Fixed in
- 3.3.7, 3.4.5, 3.5.11
MariaDB Connector/J: LOAD DATA LOCAL INFILE file check could be satisfied by text inside quoted identifiers, letting a malicious server read client files
- Affected
- >=3.0.0 <3.3.7 · >=3.4.0 <3.4.5 · >=3.5.0 <3.5.11
- Fixed in
- 3.3.7, 3.4.5, 3.5.11
MariaDB Connector/J: Server could switch character_set_results away from UTF-8 without the client noticing
- Affected
- >=3.0.0 <3.3.7 · >=3.4.0 <3.4.5 · >=3.5.0 <3.5.11
- Fixed in
- 3.3.7, 3.4.5, 3.5.11
MariaDB Connector/J does not enforce allowLocalInfile=false on server-initiated LOCAL INFILE requests
- Affected
- <2.7.14 · >=3.0.0 <3.3.5 · >=3.4.0 <3.4.3 · >=3.5.0 <3.5.9
- Fixed in
- 2.7.14, 3.3.5, 3.4.3, 3.5.9
org.mariadb.jdbc:mariadb-java-client has Inappropriate Encoding for Output Context
- Affected
- <2.7.14 · >=3.0.0 <3.3.5 · >=3.4.0 <3.4.3 · >=3.5.0 <3.5.9
- Fixed in
- 2.7.14, 3.3.5, 3.4.3, 3.5.9
org.mariadb.jdbc:mariadb-java-client has Cleartext Transmission of Sensitive Information and Insufficiently Protected Credentials
- Affected
- <2.7.14 · >=3.0.0 <3.3.5 · >=3.4.0 <3.4.3 · >=3.5.0 <3.5.9
- Fixed in
- 2.7.14, 3.3.5, 3.4.3, 3.5.9
MariaDB has cleartext password disclosure to a MITM on the initial-handshake
- Affected
- <2.7.14 · >=3.0.0 <3.3.5 · >=3.4.0 <3.4.3 · >=3.5.0 <3.5.9
- Fixed in
- 2.7.14, 3.3.5, 3.4.3, 3.5.9
Is your org.mariadb.jdbc:mariadb-java-client version vulnerable?
- org.mariadb.jdbc:mariadb-java-client 4.0No known advisories in 4.0.0
- org.mariadb.jdbc:mariadb-java-client 3.5No known advisories in 3.5.11
- org.mariadb.jdbc:mariadb-java-client 3.4No known advisories in 3.4.5
- org.mariadb.jdbc:mariadb-java-client 3.3No known advisories in 3.3.7
- org.mariadb.jdbc:mariadb-java-client 3.29 advisories in 3.2.0
- org.mariadb.jdbc:mariadb-java-client 3.19 advisories in 3.1.4
- org.mariadb.jdbc:mariadb-java-client 3.09 advisories in 3.0.11
- org.mariadb.jdbc:mariadb-java-client 2.7No known advisories in 2.7.15
- org.mariadb.jdbc:mariadb-java-client 2.64 advisories in 2.6.2
- org.mariadb.jdbc:mariadb-java-client 2.54 advisories in 2.5.4
- org.mariadb.jdbc:mariadb-java-client 2.44 advisories in 2.4.4
- org.mariadb.jdbc:mariadb-java-client 2.34 advisories in 2.3.0
- org.mariadb.jdbc:mariadb-java-client 2.24 advisories in 2.2.6
Which of your client projects still run an old org.mariadb.jdbc:mariadb-java-client?
NPMscan reads the pom.xml, build.gradle and gradle.lockfile in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other Maven packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Maven registry.