# CVE-2023-32784: Information disclosure in n/a

> Attackers with memory access can recover cleartext master passwords from KeePass memory dumps, compromising all stored credentials.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 May 2023
- **Updated:** 23 Jan 2025
- **Also known as:** DEBIAN-CVE-2023-32784, GHSA-f4c7-5p8v-p7jh, UBUNTU-CVE-2023-32784, openSUSE-SU-2023:0157-1, openSUSE-SU-2023:0163-1, openSUSE-SU-2024:12982-1

## What is CVE-2023-32784?

CVE-2023-32784 is a high-severity vulnerability in n/a, published on 15 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In KeePass 2.x before 2.54, it is possible to recover the cleartext master password from a memory dump, even when a workspace is locked or no longer running. The memory dump can be a KeePass process dump, swap file (pagefile.sys), hibernation file (hiberfil.sys), or RAM dump of the entire system. The first character cannot be recovered. In 2.54, there is different API usage and/or random string insertion for mitigation.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `keepass` | SUSE:Package Hub 15 SP4 | All versions | 2.54-bp154.2.3.1 |
| `keepass` | SUSE:Package Hub 15 SP5 | All versions | 2.54-bp155.2.3.1 |
| `keepass` | openSUSE:Leap 15.4 | All versions | 2.54-bp154.2.3.1 |
| `keepass` | openSUSE:Leap 15.5 | All versions | 2.54-bp155.2.3.1 |
| `keepass` | openSUSE:Tumbleweed | All versions | 2.54-1.1 |

Products: Keepass Keepass.

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

Upgrade to a fixed version.

## Is CVE-2023-32784 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-32784 exists.

Public exploit code:

- Original PoC for CVE-2023-32784 (github_poc): https://github.com/vdohney/keepass-password-dumper
- KeePass 2.X dumper (CVE-2023-32784) (github_poc): https://github.com/z-jxy/keepass_dump
- This script complements the results obtained through the keepass-password-dumper tool when exploiting the CVE-2023-32784 vulnerability affecting KeePass. (github_poc): https://github.com/und3sc0n0c1d0/BruteForce-to-KeePass
- https://github.com/mister-turtle/cve-2023-32784 (github_poc): https://github.com/mister-turtle/cve-2023-32784
- KeePass Master Password Extraction PoC for Linux (github_poc): https://github.com/CTM1/CVE-2023-32784-keepass-linux
- Re-write of original KeePass 2.X Master Password Dumper (CVE-2023-32784) POC in python. (github_poc): https://github.com/hau-zy/KeePass-dump-py

## Other vulnerabilities in n/a

- [CVE-2019-20184](https://insights.sbomify.com/CVE-2019-20184/): Other in n/a (high 7.8)
- [CVE-2017-1000066](https://insights.sbomify.com/CVE-2017-1000066/): Information disclosure in n/a (high 7.5)
- [CVE-2016-5119](https://insights.sbomify.com/CVE-2016-5119/): Code injection in n/a (high 7.5)
- [CVE-2010-5200](https://insights.sbomify.com/CVE-2010-5200/): Path traversal in n/a (medium 6.9)
- [CVE-2023-24055](https://insights.sbomify.com/CVE-2023-24055/): Information disclosure in n/a (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-32784 is a high-severity vulnerability in n/a, published on 15 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-32784 exists.

Affected product: n/a. 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-32784/ (Markdown: https://insights.sbomify.com/CVE-2023-32784/index.md)
```

## Sources

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

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