KeePass 2.35 through 2.61.1 Memory Exhaustion via KDBX Header Field Size
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| KeePass | KeePass | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Keepass | Keepass |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.168% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | KeePass versions 2.35 through 2.61.1 fail to validate KDBX header field sizes before memory allocation in the ReadHeaderField function. Attackers can craft a malicious KDBX file declaring excessive header field lengths to trigger allocation of gigabytes of memory, causing the application to consume resources and terminate. | |
| Title | KeePass 2.35 through 2.61.1 Memory Exhaustion via KDBX Header Field Size | |
| First Time appeared |
Keepass
Keepass keepass |
|
| Weaknesses | CWE-789 | |
| CPEs | cpe:2.3:a:keepass:keepass:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Keepass
Keepass keepass |
|
| References |
| |
| Metrics |
cvssV3_1
|