FKIE_CVE-2025-2506

Vulnerability from fkie_nvd - Published: 2025-05-22 16:15 - Updated: 2025-08-26 20:15
Severity ?
5.3 (Medium) - CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
Summary
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.
References
20be33e2-bf35-4d13-8fad-18bd2f3e3659https://www.enterprisedb.com/docs/security/advisories/cve20252506/
Impacted products
Vendor Product Version
To clipboard 

{
  "cveTags": [],
  "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."
    }
  ],
  "id": "CVE-2025-2506",
  "lastModified": "2025-08-26T20:15:39.743",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "HIGH",
          "attackVector": "NETWORK",
          "availabilityImpact": "NONE",
          "baseScore": 5.3,
          "baseSeverity": "MEDIUM",
          "confidentialityImpact": "HIGH",
          "integrityImpact": "NONE",
          "privilegesRequired": "LOW",
          "scope": "UNCHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N",
          "version": "3.1"
        },
        "exploitabilityScore": 1.6,
        "impactScore": 3.6,
        "source": "20be33e2-bf35-4d13-8fad-18bd2f3e3659",
        "type": "Secondary"
      }
    ]
  },
  "published": "2025-05-22T16:15:54.010",
  "references": [
    {
      "source": "20be33e2-bf35-4d13-8fad-18bd2f3e3659",
      "url": "https://www.enterprisedb.com/docs/security/advisories/cve20252506/"
    }
  ],
  "sourceIdentifier": "20be33e2-bf35-4d13-8fad-18bd2f3e3659",
  "vulnStatus": "Awaiting Analysis",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-862"
        }
      ],
      "source": "20be33e2-bf35-4d13-8fad-18bd2f3e3659",
      "type": "Secondary"
    }
  ]
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.



Detection rules are retrieved from Rulezet.