pglogical's apply worker does not sufficiently validate the length of certain fields in incoming replication protocol messages before…
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 2.4.8.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| EnterpriseDB | pglogical | >=2.0.0 <2.4.8 | 2.4.8 |
| EnterpriseDB | >=2 <2.4.8 | 2.4.8 | |
| pgEdge | >=3 <=3.3.6, >=4 <=4.1.0.3, >=5 <=5.0.11 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket