pglogical's apply worker does not sufficiently validate the length of certain fields in incoming replication protocol…
EnterpriseDB pglogical · pgEdge Spock
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| EnterpriseDB pglogical |
| No fix yet |
| pgEdge Spock |
|
|
EnterpriseDB pglogical · pgEdge Spock
| Product | Affected | Fixed in |
|---|---|---|
| EnterpriseDB pglogical |
| No fix yet |
| pgEdge Spock |
|
|
pglogical's apply worker does not sufficiently validate the length of certain fields in incoming replication protocol messages before copying them, resulting in an out-of-bounds read. A party acting as the publisher for a subscription, for example a non-PostgreSQL endpoint that speaks the pglogical replication protocol, can return crafted messages that cause the subscriber's apply worker to read beyond the bounds of an allocated buffer, disclosing adjacent process memory or crashing the worker. To exploit the issue an attacker must be able to direct a subscription at an endpoint they control. In default installations this requires privileges normally reserved for a superuser, so the issue is most relevant to managed deployments where the ability to create subscriptions has been delegated to non-superuser roles.
From the CVE record · EDB
pglogical's apply worker does not adequately validate fields in incoming replication messages before copying them. An attacker who can direct a subscription to an endpoint they control can send crafted messages that disclose adjacent process memory or crash the worker. This normally requires superuser privileges, but may be available to non-superusers in managed deployments that delegate subscription creation.
Engineers running EnterpriseDB pglogical or pgEdge Spock should check their deployments; affected versions were not specified.