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 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.

CVSS v3 5.3 MEDIUM

5.3^/10

CVSS v3 : MEDIUM

Vector :

Exploitability : 1.6 / Impact : 3.6

Attack Vector NETWORK

Attack Complexity HIGH

Privileges Required LOW

User Interaction NONE

Confidentiality Impact HIGH

Integrity Impact NONE

Availability Impact NONE

Scope UNCHANGED

References

Link	Resource
https://www.enterprisedb.com/docs/security/advisories/cve20252506/

Configurations

No configuration.

History

23 May 2025, 15:55

Type	Values Removed	Values Added
New CVE

Information

Published : 2025-05-22 16:15

Updated : 2025-05-23 15:55

NVD link : CVE-2025-2506

Mitre link : CVE-2025-2506

CVE.ORG link : CVE-2025-2506

JSON object : View

Products Affected

No product.

CWE

CWE-862

Missing Authorization

{"id": "CVE-2025-2506", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "20be33e2-bf35-4d13-8fad-18bd2f3e3659", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 5.3, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "HIGH", "availabilityImpact": "NONE", "privilegesRequired": "LOW", "confidentialityImpact": "HIGH"}, "impactScore": 3.6, "exploitabilityScore": 1.6}, {"type": "Secondary", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 5.3, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "HIGH", "availabilityImpact": "NONE", "privilegesRequired": "LOW", "confidentialityImpact": "HIGH"}, "impactScore": 3.6, "exploitabilityScore": 1.6}]}, "published": "2025-05-22T16:15:54.010", "references": [{"url": "https://www.enterprisedb.com/docs/security/advisories/cve20252506/", "source": "20be33e2-bf35-4d13-8fad-18bd2f3e3659"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Secondary", "source": "20be33e2-bf35-4d13-8fad-18bd2f3e3659", "description": [{"lang": "en", "value": "CWE-862"}]}, {"type": "Secondary", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "description": [{"lang": "en", "value": "CWE-862"}]}], "descriptions": [{"lang": "en", "value": "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.\nTo 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."}, {"lang": "es", "value": "Cuando pglogical intenta replicar datos, no verifica si est\u00e1 utilizando una conexi\u00f3n de replicaci\u00f3n. Esto significa que un usuario con acceso CONNECT a una base de datos configurada para replicaci\u00f3n puede ejecutar el comando pglogical para obtener acceso de lectura a las tablas replicadas. Al ejecutarse, pglogical deber\u00eda verificar si est\u00e1 ejecut\u00e1ndose en una conexi\u00f3n de replicaci\u00f3n, pero no realiza esta comprobaci\u00f3n. Esta vulnerabilidad se introdujo en el c\u00f3digo base de pglogical 3.x, propiedad de EDB. Este mismo c\u00f3digo base se ha integrado en BDR/PGD 4 y 5. Para explotar esta vulnerabilidad, el atacante necesita al menos permisos CONNECT a una base de datos configurada para replicaci\u00f3n, comprender varios comandos espec\u00edficos de pglogical3/BDR y ser capaz de decodificar el protocolo binario."}], "lastModified": "2025-05-23T15:55:02.040", "sourceIdentifier": "20be33e2-bf35-4d13-8fad-18bd2f3e3659"}