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!
- 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).
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.
- 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
While researching, we'd like to ask you to refrain from:
- Denial of service
- 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
firstname.lastname@example.org 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!
Hall of Fame