KeePassXC 2.7.7 kdbx Database cleartext storage in memory
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.5 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as problematic has been discovered in KeePassXC 2.7.7. This affects an unknown part of the component kdbx Database. Such manipulation leads to information disclosure. This vulnerability is uniquely identified as CVE-2024-33901. No exploit exists.
Details
A vulnerability, which was classified as problematic, has been found in KeePassXC 2.7.7. Affected by this issue is an unknown functionality of the component kdbx Database. The manipulation with an unknown input leads to a information disclosure vulnerability. Using CWE to declare the problem leads to CWE-316. The product stores sensitive information in cleartext in memory. Impacted is confidentiality. CVE summarizes:
Issue in KeePassXC 2.7.7 allows an attacker (who has the privileges of the victim) to recover some passwords stored in the .kdbx database via a memory dump. NOTE: the vendor disputes this because memory-management constraints make this unavoidable in the current design and other realistic designs.
The advisory is available at keepassxc.org. This vulnerability is handled as CVE-2024-33901 since 04/28/2024. The technical details are unknown and an exploit is not available. This vulnerability is assigned to T1555 by the MITRE ATT&CK project.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.5VulDB Meta Temp Score: 3.5
VulDB Base Score: 3.5
VulDB Temp Score: 3.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Cleartext storage in memoryCWE: CWE-316 / CWE-312 / CWE-310
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
04/28/2024 🔍05/21/2024 🔍
05/21/2024 🔍
06/13/2025 🔍
Sources
Advisory: keepassxc.orgStatus: Not defined
CVE: CVE-2024-33901 (🔍)
GCVE (CVE): GCVE-0-2024-33901
GCVE (VulDB): GCVE-100-265322
Entry
Created: 05/21/2024 06:47Updated: 06/13/2025 18:26
Changes: 05/21/2024 06:47 (48), 07/29/2024 19:06 (2), 06/13/2025 18:26 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.