# CVE-2023-22332: Information disclosure in Pgpool-II

> A remote attacker can obtain another user's authentication credentials, leading to unauthorized data access, modification, or database suspension.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Jan 2023
- **Updated:** 3 Nov 2025
- **Also known as:** DEBIAN-CVE-2023-22332, GHSA-w496-f5jm-w9c3, UBUNTU-CVE-2023-22332

## What is CVE-2023-22332?

CVE-2023-22332 is a medium-severity vulnerability in Pgpool-II, published on 30 Jan 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Information disclosure vulnerability exists in Pgpool-II 4.4.0 to 4.4.1 (4.4 series), 4.3.0 to 4.3.4 (4.3 series), 4.2.0 to 4.2.11 (4.2 series), 4.1.0 to 4.1.14 (4.1 series), 4.0.0 to 4.0.21 (4.0 series), All versions of 3.7 series, All versions of 3.6 series, All versions of 3.5 series, All versions of 3.4 series, and All versions of 3.3 series. A specific database user's authentication information may be obtained by another database user. As a result, the information stored in the database may be altered and/or database may be suspended by a remote attacker who successfully logged in the product with the obtained credentials.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information)

## Which versions are affected by CVE-2023-22332?

It affects 1 product.


Products: Pgpool Pgpool-Ii.

## How do I fix CVE-2023-22332?

Upgrade to a fixed version.

## Is CVE-2023-22332 being exploited?

There is no known exploitation of CVE-2023-22332 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-22332 and fix it if it is affected.

What it is: CVE-2023-22332 is a medium-severity vulnerability in Pgpool-II, published on 30 Jan 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-22332 in the wild and no public exploit code.

Affected product: Pgpool-II. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-22332/ (Markdown: https://insights.sbomify.com/CVE-2023-22332/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-22332
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-22332
- OSV: https://osv.dev/vulnerability/CVE-2023-22332

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-22332/
Summaries are generated and may contain mistakes; the official description above is the record.