Metrics
Affected Vendors & Products
Fri, 18 Jul 2025 19:00:00 +0000
Type | Values Removed | Values Added |
---|---|---|
First Time appeared |
Broadcom bitnami\/pgpool
|
|
CPEs | cpe:2.3:a:broadcom:bitnami\/pgpool:*:*:*:*:*:docker:*:* | |
Vendors & Products |
Broadcom bitnami Popool
|
Broadcom bitnami\/pgpool
|
Wed, 16 Jul 2025 18:45:00 +0000
Type | Values Removed | Values Added |
---|---|---|
First Time appeared |
Broadcom
Broadcom bitnami Broadcom bitnami Popool |
|
CPEs | cpe:2.3:a:broadcom:bitnami:*:*:*:*:*:postgresql:*:* cpe:2.3:a:broadcom:bitnami_popool:*:*:*:*:*:docker:*:* |
|
Vendors & Products |
Broadcom
Broadcom bitnami Broadcom bitnami Popool |
|
Metrics |
cvssV3_1
|
Tue, 13 May 2025 14:15:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Metrics |
ssvc
|
Tue, 13 May 2025 13:45:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Weaknesses | CWE-1188 |
Tue, 13 May 2025 09:30:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Description | The bitnami/pgpool Docker image, and the bitnami/postgres-ha k8s chart, under default configurations, comes with an 'repmgr' user that allows unauthenticated access to the database inside the cluster. The PGPOOL_SR_CHECK_USER is the user that Pgpool itself uses to perform streaming replication checks against nodes, and should not be at trust level. This allows to log into a PostgreSQL database using the repgmr user without authentication. If Pgpool is exposed externally, a potential attacker could use this user to get access to the service. This is also present within the bitnami/postgres-ha Kubernetes Helm chart. | |
Title | [pgpool] Unauthenticated access to postgres through pgpool | |
References |
| |
Metrics |
cvssV4_0
|

Status: PUBLISHED
Assigner: vmware
Published:
Updated: 2025-05-13T13:10:31.070Z
Reserved: 2025-01-02T04:30:19.929Z
Link: CVE-2025-22248

Updated: 2025-05-13T13:10:26.931Z

Status : Analyzed
Published: 2025-05-13T10:15:22.600
Modified: 2025-07-18T18:58:21.510
Link: CVE-2025-22248

No data.