MariaDB Connector/Node.js exposes uninitialized process memory through malformed GeoJSON parameters
mariadb-corporation mariadb-connector-nodejs
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| mariadb npm |
|
|
mariadb-corporation mariadb-connector-nodejs
| Product | Affected | Fixed in |
|---|---|---|
| mariadb npm |
|
|
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.
From the CVE record · GitHub_M
The GeoJSON Polygon and MultiPolygon binary encoders can include uninitialized Node.js heap data in a database value when a malformed, non-array ring is passed through execute() or batch(). The stored data may contain sensitive information and may propagate to backups and replicas. The text-protocol query() path is not affected.
Check applications using the npm mariadb package in versions below 3.2.5, from 3.3.0 to below 3.3.4, from 3.4.0 to below 3.4.7, or from 3.5.0-rc.0 to below 3.5.4.