Approved changes feed: RSS · Atom
cpe:2.3:a:broadcom:bitnami:*:*:*:*:*:postgresql:*:*
part: a version: * update: *
| Vendor | Broadcom (9814e701-1071-5d68-93ef-4536eaf59407) |
|---|---|
| Product | Bitnami (219fa24b-9cad-5ffa-b6b7-7310604b8927) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | postgresql |
| 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-22248 |
vulnerable | 2026-06-08 07:10:52.535080 |
[pgpool] Unauthenticated access to postgres through pgpool
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.
Published: 2025-05-13T09:13:30.613Z
Updated: 2025-05-13T13:10:31.070Z |
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.