{"answers":{"affected":"1 open source package ship an affected version, including pgpool. It affects 2 products.","exploited":"There is no known exploitation of CVE-2025-22248 in the wild and no public exploit code.","fix":"Upgrade pgpool to 4.6.0-1 or later.","what":"CVE-2025-22248 is a critical authentication bypass vulnerability in VMware Bitnami, published on 13 May 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-22248 and fix it if it is affected.\n\nWhat it is: CVE-2025-22248 is a critical authentication bypass vulnerability in VMware Bitnami, published on 13 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-22248 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- pgpool (Bitnami): affected all versions; fixed in 4.6.0-1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-22248/ (Markdown: https://insights.sbomify.com/CVE-2025-22248/index.md)","id":"CVE-2025-22248","markdown":"https://insights.sbomify.com/CVE-2025-22248/index.md","name":"CVE-2025-22248","record":{"aliases":["BIT-pgpool-2025-22248","GHSA-mx38-x658-5fwj"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"configuration_change","impacts":["data_read","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Bitnami pgpool image","requires_auth":"none","summary":"Unauthenticated access to PostgreSQL via the repmgr user in default Bitnami pgpool configurations allows attackers to read and modify database data.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"vmware","cpe":[{"product":"bitnami","vendor":"broadcom"},{"product":"bitnami\\/pgpool","vendor":"broadcom"}],"cvss":{"score":9.4,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H","version":"4.0"},"cwes":[{"id":"CWE-1188","name":"Initialization of a Resource with an Insecure Default"}],"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.","ecosystems":["Bitnami"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"[pgpool] Unauthenticated access to postgres through pgpool","id":"CVE-2025-22248","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":"auth_bypass","year":"2025"},"n_packages":1,"n_references":1,"next":{"headline":"VMSA-2025-0008: VMware Aria automation updates address a DOM based Cross-site scripting vulnerability (CVE-2025-22249)","id":"CVE-2025-22249"},"packages":[{"ecosystem":"Bitnami","fixed":["4.6.0-1"],"introduced":["0"],"last_affected":[],"package":"pgpool","purl":"pkg:bitnami/pgpool","source":"BIT-pgpool-2025-22248"}],"prev":{"headline":"Insecure file handling vulnerability","id":"CVE-2025-22247"},"products":["Bitnami"],"published":"2025-05-13","related":[],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-05-13","vendors":["VMware"]},"summary":"Unauthenticated access to PostgreSQL via the repmgr user in default Bitnami pgpool configurations allows attackers to read and modify database data.","url":"https://insights.sbomify.com/CVE-2025-22248/"}