# CVE-2021-22030: Information disclosure in GPDB (Greenplum database)

> Attackers with log access can read sensitive user credentials stored in database logs due to improper handling of certain statements.

- **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:** No
- **Published:** 19 Nov 2021
- **Updated:** 3 Aug 2024

## What is CVE-2021-22030?

CVE-2021-22030 is a medium-severity vulnerability in GPDB (Greenplum database), published on 19 Nov 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In versions of Greenplum database prior to 5.28.14 and 6.17.0, certain statements execution led to the storage of sensitive(credential) information in the logs of the database. A malicious user with access to logs can read sensitive(credentials) information about users

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2021-22030?

It affects 1 product.


Products: Greenplum Greenplum.

## How do I fix CVE-2021-22030?

No fix has been published for CVE-2021-22030 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-22030 being exploited?

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

## Other vulnerabilities in GPDB (Greenplum database)

- [CVE-2021-22028](https://insights.sbomify.com/CVE-2021-22028/): Path traversal in gpfdist (Greenplum) (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-22030 and fix it if it is affected.

What it is: CVE-2021-22030 is a medium-severity vulnerability in GPDB (Greenplum database), published on 19 Nov 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-22030 in the wild and no public exploit code.

Affected product: GPDB (Greenplum database). 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-2021-22030/ (Markdown: https://insights.sbomify.com/CVE-2021-22030/index.md)
```

## Sources

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

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