# CVE-2024-33900: Information disclosure in n/a

> An attacker with local access can recover cleartext credentials from memory dumps in KeePassXC, exposing sensitive password data.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 May 2024
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-c45j-7735-f4r2

## What is CVE-2024-33900?

CVE-2024-33900 is a medium-severity vulnerability in n/a, published on 20 May 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

KeePassXC 2.7.7 allows an attacker (who has the privileges of the victim) to recover cleartext credentials via a memory dump. NOTE: the vendor disputes this because memory-management constraints make this unavoidable in the current design and other realistic designs.

Weakness: CWE-316 (Cleartext Storage of Sensitive Information in Memory)

## Which versions are affected by CVE-2024-33900?

It affects 1 product.


Products: Keepassxc Keepassxc.

## How do I fix CVE-2024-33900?

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

## Is CVE-2024-33900 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-33901](https://insights.sbomify.com/CVE-2024-33901/): Information disclosure in n/a (medium 6.5)
- [CVE-2023-35866](https://insights.sbomify.com/CVE-2023-35866/): Security feature bypass in n/a (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-33900 and fix it if it is affected.

What it is: CVE-2024-33900 is a medium-severity vulnerability in n/a, published on 20 May 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-33900 in the wild and no public exploit code.

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-2024-33900/ (Markdown: https://insights.sbomify.com/CVE-2024-33900/index.md)
```

## Sources

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

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