Mariadb-corporation mariadb-connector-nodejs
MariaDB Connector/Node.js exposes uninitialized process memory through malformed GeoJSON parameters
MariaDB Connector/Node.js is used to connect applications developed on Node.js to MariaDB and MySQL databases. Prior to 3.2.5, 3.3.4, 3.4.7, and 3.5.4, the GeoJSON Polygon and MultiPolygon binary encoders size a Buffer.allocUnsafe() allocation from each ring's numeric length before confirming that the ring is an array. A malformed non-array ring can therefore reserve bytes that the writing loop skips, and the connector sends the full buffer through execute() or batch(), disclosing uninitialized Node.js heap data into a database value. The persisted data can include other users' content, session material, database credentials, or TLS key material and may propagate to backups and replicas. The text-protocol query() path is not affected. This issue is fixed in versions 3.2.5, 3.3.4, 3.4.7, and 3.5.4.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 3.2.5
- >= 3.3.0, < 3.3.4
- >= 3.4.0, < 3.4.7
- >= 3.5.0-rc.0, < 3.5.4
Fixed in 3.2.5, 3.3.4, 3.4.7, 3.5.4
Mitigation
Upgrade mariadb-connector-nodejs to 3.2.5 or 3.3.4 or 3.4.7 or 3.5.4 or later.
References
- Vendor advisory github.com/mariadb-corporation/mariadb-connect…
- Patch github.com/mariadb-corporation/mariadb-connect…
- Patch github.com/mariadb-corporation/mariadb-connect…
5 more
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.