CVE-2024-33669 — passbolt-browser-extension
MEDIUMCVE-2024-33669 is a medium-severity (CVSS 6.1) Information Exposure vulnerability in passbolt-browser-extension. A fix is available for passbolt-browser-extension — see the affected versions and patch details below.
Passbolt Browser Extension leaks password information
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-33669.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
passbolt-browser-extensionnpmDescription
An issue was discovered in Passbolt Browser Extension before 4.6.2. It can send multiple requests to HaveIBeenPwned while a password is being typed, which results in an information leak. This allows an attacker capable of observing Passbolt's HTTPS queries to the Pwned Password API to more easily brute force passwords that are manually typed by the user.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | passbolt-browser-extension | all versions | 4.6.2npm install passbolt-browser-extension@4.6.2 |
Affected Products
passbolt browser extensionpassboltDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for passbolt-browser-extension, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update passbolt-browser-extension to 4.6.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-33669 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.
Frequently Asked Questions
Is CVE-2024-33669 in your dependencies?
Find it across npm, including transitive dependencies.