Keepassxc: Browser integration leaking informations

Created on 27 Aug 2019  路  3Comments  路  Source: keepassxreboot/keepassxc

Expected Behavior

When I have several databases opened in KeepassXC, KeepassXC-Browser get passwords of the active database (selected tab) if a key is present in KeepassXC-Browser settings of the active database.

Current Behavior

When I have several databases opened in KeepassXC, KeepassXC-Browser get passwords of the active database (selected tab) if a key is present in KeepassXC-Browser settings of any open database.

Steps to Reproduce

  1. Open a DB: DB1. Connect this DB to KeepassXC-Browser. This DB contains a password for website.com
  2. Open a DB: DB2. Do not connect this DB to KeepassXC-Browser. This DB contains a password for website.com
  3. When browsing website.com and active DB is DB2, KeepassXC-Browser know the password in DB2.

Context

When accessing a password of a database not connected (DB2), KeepassXC-Browser says it is connected to Keepass with a key named "Firefox". This key does not exists in any of my settings.

This bug is intermittent and I do not know exactly how to trigger it.

Debug Info

KeePassXC - Version 2.4.3
Revision: 5d6ef0c

Qt 5.9.5
Debugging mode is disabled.

Operating system: Ubuntu 18.04.3 LTS
CPU architecture: x86_64
Kernel: linux 4.15.0-58-generic

Enabled extensions:

  • Auto-Type
  • Browser Integration
  • SSH Agent
  • KeeShare (signed and unsigned sharing)
  • YubiKey

Cryptographic libraries:
libgcrypt 1.8.1

bug Browser integration security

Most helpful comment

That's ironic

All 3 comments

I'll fix this ASAP. It's probably related to the change where the restriction accessing multiple databases were introduced.

Steps to reproduce:

  1. Open a connected DB
  2. Switch tab to non-open non-connected DB2
  3. Open DB2

If "Search in all opened databases for matching credentials" is checked, the bug doesn't trigger.

That's ironic

Was this page helpful?
0 / 5 - 0 ratings