# CVE-2022-43930: IBM Db2 for Linux, UNIX and Windows information disclosure

> Attackers can read sensitive information from log files in IBM Db2 for Linux, UNIX, and Windows.

- **Severity:** Medium 6.2 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Feb 2023
- **Updated:** 12 Mar 2025
- **Also known as:** GHSA-xc88-8xhr-v9x4

## What is CVE-2022-43930?

CVE-2022-43930 is a medium-severity vulnerability in Ibm Db2, published on 17 Feb 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

IBM Db2 for Linux, UNIX and Windows 10.5, 11.1, and 11.5 is vulnerable to an Information Disclosure as sensitive information may be included in a log file.  IBM X-Force ID:  241677.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2022-43930?

It affects 1 product.


Products: Ibm Db2.

## How do I fix CVE-2022-43930?

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

## Is CVE-2022-43930 being exploited?

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

## Other vulnerabilities in Ibm Db2

- [CVE-2012-1797](https://insights.sbomify.com/CVE-2012-1797/): IBM DB2 9.5 uses world-writable permissions for nodes.reg, which has unspecified impact and attack vectors. (critical 10.0)
- [CVE-2010-3731](https://insights.sbomify.com/CVE-2010-3731/): Memory corruption in n/a (critical 10.0)
- [CVE-2010-3193](https://insights.sbomify.com/CVE-2010-3193/): Other in n/a (critical 10.0)
- [CVE-2009-4335](https://insights.sbomify.com/CVE-2009-4335/): Other in n/a (critical 10.0)
- [CVE-2009-3473](https://insights.sbomify.com/CVE-2009-3473/): Missing authorization in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-43930 and fix it if it is affected.

What it is: CVE-2022-43930 is a medium-severity vulnerability in Ibm Db2, published on 17 Feb 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-43930 in the wild and no public exploit code.

Affected product: Ibm Db2. 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-2022-43930/ (Markdown: https://insights.sbomify.com/CVE-2022-43930/index.md)
```

## Sources

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

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