Skip to content

CVE-2025-2506 When pglogical attempts to replicate data, it does not verify it is using a replication connection, which means a user with CONNECT access to a database configured for replication can execute the pglo...

MediumCVSS 5.3 EPSS 0.33%
Published
Updated
Exploit status
No public exploit known
CISA SSVC
No known exploitation · automatable: no · technical impact: partial
Technology
Debian

Description

When pglogical attempts to replicate data, it does not verify it is using a replication connection, which means a user with CONNECT access to a database configured for replication can execute the pglogical command to obtain read access to replicated tables. When pglogical runs it should verify it is running on a replication connection but does not perform this check. This vulnerability was introduced in the pglogical 3.x codebase, which is proprietary to EDB. The same code base has been integrated into BDR/PGD 4 and 5.
To exploit the vulnerability the attacker needs at least CONNECT permissions to a database configured for replication and must understand a number of pglogical3/BDR specific commands and be able to decode the binary protocol.

Upgrade path

2 packages: 2 fixed.

PackageAffectedFixed inStatus
EnterpriseDB BDR/PGD >= 4, < 4.3.8-ELS; >= 5, < 5.8.0 4.3.8-ELS, 5.8.0 Fixed
EnterpriseDB pglogical >= 3, < 3.7.26-ELS 3.7.26-ELS Fixed

Affected products

ProductAffected versionsFixed in
EnterpriseDB pglogical >= 3, < 3.7.26-ELS 3.7.26-ELS
EnterpriseDB BDR/PGD >= 4, < 4.3.8-ELS 4.3.8-ELS
EnterpriseDB BDR/PGD >= 5, < 5.8.0 5.8.0

References