Skip to content
OpenAdvisories
High · 7.5 Public exploit CVE-2023-32784 EUVD-2023-37007GHSA-f4c7-5p8v-p7jh

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 …

Published May 15, 2023 · Updated Jan 23, 2025 · Assigned by mitre

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.

Fixed in Linux distributions

Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.

ReleasePackageFixed inAdvisory
Debian 14 keepass2 No fix yet —
Debian 13 keepass2 No fix yet —
Debian 12 keepass2 No fix yet —
ReleasePackageFixed inAdvisory
Ubuntu 26.10 keepass2 No fix yet —
Ubuntu 26.04 LTS keepass2 No fix yet —
Ubuntu 25.10 keepass2 No fix yet —
Ubuntu 24.04 LTS keepass2 No fix yet —
Ubuntu 22.04 LTS keepass2 No fix yet —
Show 3 more (older releases, extended support, other products)
ReleasePackageFixed inAdvisory
Ubuntu 20.04 LTS keepass2 No fix yet —
Ubuntu 18.04 LTS keepass2 No fix yet —
Ubuntu 16.04 LTS keepass2 No fix yet —
ReleasePackageFixed inAdvisory
SUSE Package Hub 15 SP5 keepass 2.54-bp155.2.3.1 openSUSE-SU-2023:0163-1
SUSE Package Hub 15 SP4 keepass 2.54-bp154.2.3.1 openSUSE-SU-2023:0157-1
ReleasePackageFixed inAdvisory
openSUSE Tumbleweed keepass 2.54-1.1 openSUSE-SU-2024:12982-1
openSUSE Leap 15.5 keepass 2.54-bp155.2.3.1 openSUSE-SU-2023:0163-1
openSUSE Leap 15.4 keepass 2.54-bp154.2.3.1 openSUSE-SU-2023:0157-1

Public exploits

Exploit or proof-of-concept code for this vulnerability is publicly available, which lowers the bar for attackers. Treat it as a reason to patch sooner.

Third-party code, not reviewed by us. Public PoCs are sometimes fake or contain malware. Read the code first and run it only in an isolated lab, against systems you are authorised to test.

GitHub 14 repositories · most starred shown

Sources: PoC-in-GitHub, Metasploit Framework, Exploit-DB — updated daily. Only links are listed; no exploit code is hosted here.

Advisories 4

References