Improper Handling of Length Parameter Inconsistency Affecting mariadb:10.3/mariadb-embedded-devel package, versions *


Severity

Recommended
0.0
medium
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.36% (31st percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL8-MARIADB-22300385
  • published8 Nov 2026
  • disclosed29 Oct 2026

Introduced: 29 Oct 2026

NewCVE-2026-119278  (opens in a new tab)
CWE-130  (opens in a new tab)

How to fix?

There is no fixed version for RHEL:8 mariadb:10.3/mariadb-embedded-devel.

NVD Description

Note: Versions mentioned in the description apply only to the upstream mariadb:10.3/mariadb-embedded-devel package and not the mariadb:10.3/mariadb-embedded-devel package as distributed by RHEL. See How to fix? for RHEL:8 relevant fixed versions and status.

MariaDB Connector/J is used to connect applications developed in Java to MariaDB and MySQL databases. From 3.0.0 until 3.3.7 and 3.4.5, during caching_sha2_password authentication, the authentication-more-data response was treated as a length-encoded byte array, memory was allocated from the server-declared length, and authResult[0] was accessed without ensuring a byte existed. A malicious or compromised server, or a machine-in-the-middle attacker, could declare a very large length or send an empty response before any password was transmitted. The malformed packet could cause excessive allocation or an unchecked ArrayIndexOutOfBoundsException escaping from DriverManager.getConnection(). This issue is fixed in versions 3.3.7 and 3.4.5.

CVSS Base Scores

version 3.1