Skip to content

mysql_json plugin OOB reads

Moderate
vuvova published GHSA-89ph-64cf-gqcc Sep 7, 2026

Package

No package listed

Affected versions

10.6.1-10.6.27, 10.11.1-10.11.18, 11.4.1-11.4.12, 11.8.1-11.8.8, 12.3.1-12.3.2, 13.0.1

Patched versions

10.6.28, 10.11.19, 11.4.13, 11.8.9, 12.3.3, 13.0.2

Description

Impact

mysql_json plugin, which is used to parse MySQL binary json data format was assuming the table is a valid MySQL table with JSON columns. A specially prepared MySQL table with invalid JSON data could have caused it to perform OOB reads.

Patches

Fixed in 10.6.28, 10.11.19, 11.4.13, 11.8.9, 12.3.3, 13.0.2.

Workarounds

Do not install mysql_json plugin unless you need to convert MySQL tables with binary JSON columns into MariaDB format. Uninstall the plugin after the migration.
Make sure FILE privilege and secure-file-priv setting are configured correctly to disallow writes into the datadir.
Make sure local filesystem privileges don't allow local users to create files in the datadir.

References

https://jira.mariadb.org/browse/MDEV-40678

Credits

Reported by Yuelin Wang

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Local
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
Low

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:L

CVE ID

No known CVE

Weaknesses

Out-of-bounds Read

The product reads data past the end, or before the beginning, of the intended buffer. Learn more on MITRE.