Approved changes feed: RSS · Atom
cpe:2.3:a:enterprisedb:bdr/pgd:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Enterprisedb (788c5be5-c3bc-5186-8634-02d14556d9dc) |
|---|---|
| Product | Bdr/Pgd (688a7bb2-0248-5829-8dae-c97388d483eb) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2025-2506 |
vulnerable | 2026-06-08 07:16:57.152033 |
Details available
MEDIUM (5.3)
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.
Published: 2025-05-22T15:22:20.041Z
Updated: 2025-08-26T19:26:48.602Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.