KeePassXC: Out-of-bounds write in browser integration response encryption with oversized database responses
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2.8.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
KeePassXC, a cross-platform password manager, is affected through its browser integration feature, which encrypts responses to browser clients. A client with access to the per-user IPC endpoint and a valid database association could trigger an out-of-bounds memory write, potentially corrupting memory in the application.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
KeePassXC is a cross-platform community-driven port of the Windows application KeePass Password Safe. From 2.3.0 until 2.8.0, KeePassXC browser integration encrypts authorized responses in src/browser/BrowserMessageBuilder.cpp using a fixed 1 MiB output vector even though Botan::Sodium::crypto_box_easy() writes the plaintext length plus crypto_box_MACBYTES. A browser-protocol client that can access the per-user IPC endpoint, has a valid database association, and causes an unlocked database to generate and encrypt a sufficiently large authorized response can trigger a sequential out-of-bounds write before any response is delivered. This issue is fixed in version 2.8.0.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- keepassxreboot keepassxc
From 2.3.0 · fixed in 2.8.0