Bitwarden believes that working with security researchers across the globe is crucial to keeping our users safe. If you believe you've found a security issue in our product or service, we encourage you to notify us. We welcome working with you to resolve the issue promptly. Thanks in advance!

Disclosure Policy

• Let us know as soon as possible upon discovery of a potential security issue, and we'll make every effort to quickly resolve the issue.

• Provide us a reasonable amount of time to resolve the issue before any disclosure to the public or a third-party. We may publicly disclose the issue before resolving it, if appropriate.

• Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service. Only interact with accounts you own or with explicit permission of the account holder.

• If you would like to encrypt your report, please use the PGP key with long ID 0xDE6887086F892325FEC04CC0D847525B6931381F (available in the public keyserver pool).

In-scope

• Security issues in any current release of Bitwarden. This includes the web vault, browser extension, and mobile apps (iOS and Android). Product downloads are available at https://bitwarden.com. Source code is available at https://github.com/bitwarden.

Exclusions

The following bug classes are out-of scope:

• Bugs that are already reported on any of Bitwarden's issue trackers (https://github.com/bitwarden), or that we already know of. Note that some of our issue tracking is private.

• Issues in an upstream software dependency (ex: Xamarin, ASP.NET) which are already reported to the upstream maintainer.

• Attacks requiring physical access to a user's device.

• Self-XSS

• Username/email enumeration

• Issues related to software or protocols not under Bitwarden's control

• Vulnerabilities in outdated versions of Bitwarden

• Missing security best practices that do not directly lead to a vulnerability

• Missing HTTP security headers (https://www.owasp.org/index.php/List_of_useful_HTTP_headers), ex. * Strict-Transport-Security, X-Frame-Options, X-XSS-Protection, Content-Security-Policy, Content-Security-Policy, etc.

• CSV injection

• Lack of Secure/HTTPOnly flags on non-sensitive cookies

• Issues that do not have any impact on the general public

• Any activity that could lead to the disruption of our service (DoS)

• Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS

• Rate limiting or bruteforce issues on non-authentication endpoints

• Issues that require unlikely user interaction

• Authorization state and session expiration on bearer tokens

• Unencrypted authentication tokens

• KDF count disclosure on /prelogin API from server

• Race conditions affecting business logic

• Exposing "hidden" passwords through client-side manipulation

• DMARC, SPF or other email server or DNS configuration settings and policies

• Recommendations or concerns over sweeping areas of the application’s architecture and/or design

• Scenarios that are extremely complex, difficult or unlikely when utilizing already compromised administrative accounts, self-hosted server, networks or physical devices which would render much easier and alternate means of compromising the data contained within Bitwarden

• Client manipulation or other techniques that lead to the use of premium features not otherwise enabled or allowed

While researching, we'd like to ask you to refrain from:

• Denial of service

• Spamming

• Social engineering (including phishing) of Bitwarden staff or contractors

• Any physical attempts against Bitwarden property or data centers

A note on rate limiting

There is rate limiting present on the application, so be careful in running scanners or anything that might send an excessive number of requests and add additional waiting to your testing. If you exceed the rate limit too often your IP will be banned. For this program we request that you submit flaw hypotheses for any enumeration vulnerabilities you believe you have found.

We want to help you!

If you have something that you feel is close to exploitation, or if you'd like some information regarding the internal API, or generally have any questions regarding the app that would help in your efforts, please email us at https://bitwarden.com/contact and ask for that information. As stated above, Bitwarden wants to help you find issues, and is more than willing to help.

Thank you for helping keep Bitwarden and our users safe!