PgPointcloud (<= 1.2.5) - CraftedSignal Threat Feedhttps://feed.craftedsignal.io/products/pgpointcloud--1.2.5/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioFri, 25 Sep 2026 22:55:24 +0000https://feed.craftedsignal.io/favicon-32x32.pngCraftedSignal Threat Feedhttps://feed.craftedsignal.io/3232https://feed.craftedsignal.io/favicon.svgHeap Out-of-Bounds Read in pgPointcloudhttps://feed.craftedsignal.io/briefs/2026-09-pgpointcloud-oob/Fri, 25 Sep 2026 22:55:24 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-09-pgpointcloud-oob/pgPointcloud versions through 1.2.5 contain a heap out-of-bounds read vulnerability in WKB deserialization that allows authenticated database users to exfiltrate heap memory or trigger backend service crashes.pgPointcloud through version 1.2.5 is susceptible to a heap out-of-bounds read vulnerability occurring during the deserialization of dimensional patch Well-Known Binary (WKB) data. This flaw stems from improper handling of size fields within the input data, which can be manipulated by an authenticated database user. By providing a crafted pcpatch value, an attacker can trick the PostgreSQL backend into reading and returning memory addresses outside of the allocated buffer. This can result in the leakage of sensitive data stored in the database heap or the termination of the backend process, leading to a denial-of-service condition. This vulnerability is significant for organizations utilizing the pgPointcloud extension for spatial data processing, as it permits unauthorized access to database memory from within the database environment.

Impact

Successful exploitation allows an authenticated user to perform unauthorized information disclosure by reading adjacent memory segments, potentially exposing credentials, cryptographic keys, or sensitive records. Furthermore, the ability to induce an out-of-bounds read often leads to memory corruption, enabling attackers to crash the PostgreSQL backend service, which disrupts database availability for all users.

Recommendation

Prioritized actions include:

  • Update the pgPointcloud extension to the latest secure version addressing this vulnerability once available.
  • Review database access controls and minimize privileges for users with the ability to execute spatial functions or interact with pgPointcloud objects.
  • Monitor PostgreSQL logs for frequent backend crashes or service restarts that may indicate attempted exploitation of this memory corruption vulnerability.
]]>highadvisory