Vulnerability from bitnami_vulndb
Published
2025-05-13 07:30
Modified
2025-05-13 07:30
Summary
Details
The PgPool II component into a Bitnami Pgpool II container image comes by default configured with an 'repmgr' user that allows unauthenticated access to the database inside the cluster. This can be addressed by mounting and overwriting the Pgpool configuration file directly. If PgPool is exposed externally, a potential attacker could use this user to get access to the service.
{
"affected": [
{
"package": {
"ecosystem": "Bitnami",
"name": "pgpool",
"purl": "pkg:bitnami/pgpool"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "4.6.0-1"
}
],
"type": "SEMVER"
}
],
"severity": [
{
"score": "CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/CR:H/IR:H/AR:H/MAV:A/MAC:L/MAT:N/MPR:N/MUI:N/MVC:H/MVI:H/MVA:H/MSC:H/MSI:H/MSA:H",
"type": "CVSS_V4"
}
]
}
],
"aliases": [
"CVE-2025-22248"
],
"database_specific": {
"cpes": [
"cpe:2.3:*:pgpool:pgpooladmin:*:*:*:*:*:*:*:*"
],
"severity": "Critical"
},
"details": "The PgPool II component into a Bitnami Pgpool II container image comes by default configured with an \u0027repmgr\u0027 user that allows unauthenticated access to the database inside the cluster. This can be addressed by mounting and overwriting the Pgpool configuration file directly. If PgPool is exposed externally, a potential attacker could use this user to get access to the service.",
"id": "BIT-pgpool-2025-22248",
"modified": "2025-05-13T07:30:00.000Z",
"published": "2025-05-13T07:30:00.000Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/bitnami/charts/security/advisories/GHSA-mx38-x658-5fwj"
}
],
"schema_version": "1.6.2"
}
Loading…
Loading…
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.
Loading…
Loading…