https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 11 Oct 2026 23:48:52 +0000 https://vulnerability.circl.lu/vuln/fkie_cve-2026-107383 <p>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&#39;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&#39; 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.</p> <p>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&#39;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&#39; 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.</p> https://vulnerability.circl.lu/vuln/fkie_cve-2026-107383 https://vulnerability.circl.lu/vuln/ghsa-48qf-xh34-q73r <p><strong>Affected:</strong> npm: mariadb</p> <p>### Description When encoding a GeoJSON Polygon or MultiPolygon parameter for the binary protocol, the connector sized its output buffer from the length property of each ring, then wrote each ring only if it was a real array. The two loops disagreed: any non-array ring carrying a numeric length (a string, or an object such as {&#34;length&#34;: 4000}) still reserved 4 + 16 * length bytes, but wrote none of them. The buffer came from Buffer.allocUnsafe() and was returned in full regardless of how far the write position had advanced, so every reserved-but-unwritten byte was uninitialized Node.js heap.</p> <p>The sibling LineString case handled this correctly, aborting with null on the first malformed point, so no reserved byte could escape unwritten.</p> <p>The only gate on this path is value.type naming a GeoJSON type, so any object shaped like {&#34;type&#34;: &#34;Polygon&#34;, ...} reached the encoder.</p> <p>### Impact An application that passes an attacker-influenced object as a parameter to execute() or batch() writes uninitialized process memory into the database, where it is readable by anyone who can read that row and persists into backups and replicas. Applications accepting GeoJSON for map or location features are the natural case, as the attacker controls coordinates directly.</p> <p>The disclosed memory is not scoped to the requesting user: in a shared Node.js process the heap may hold other users&#39; request and response bodies, session tokens and cookies, database credentials and TLS key material. The leak is s…</p> <p><strong>Affected:</strong> npm: mariadb</p> <p>### Description When encoding a GeoJSON Polygon or MultiPolygon parameter for the binary protocol, the connector sized its output buffer from the length property of each ring, then wrote each ring only if it was a real array. The two loops disagreed: any non-array ring carrying a numeric length (a string, or an object such as {&#34;length&#34;: 4000}) still reserved 4 + 16 * length bytes, but wrote none of them. The buffer came from Buffer.allocUnsafe() and was returned in full regardless of how far the write position had advanced, so every reserved-but-unwritten byte was uninitialized Node.js heap.</p> <p>The sibling LineString case handled this correctly, aborting with null on the first malformed point, so no reserved byte could escape unwritten.</p> <p>The only gate on this path is value.type naming a GeoJSON type, so any object shaped like {&#34;type&#34;: &#34;Polygon&#34;, ...} reached the encoder.</p> <p>### Impact An application that passes an attacker-influenced object as a parameter to execute() or batch() writes uninitialized process memory into the database, where it is readable by anyone who can read that row and persists into backups and replicas. Applications accepting GeoJSON for map or location features are the natural case, as the attacker controls coordinates directly.</p> <p>The disclosed memory is not scoped to the requesting user: in a shared Node.js process the heap may hold other users&#39; request and response bodies, session tokens and cookies, database credentials and TLS key material. The leak is s…</p> https://vulnerability.circl.lu/vuln/ghsa-48qf-xh34-q73r