Mirrors/Vaultwarden
1
0
Fork 0
mirror of https://github.com/dani-garcia/vaultwarden.git synced 2024-11-23 19:32:40 +01:00
Code Issues Releases Activity
register_verify_email
Vaultwarden/SECURITY.md
Mathijs van Veluw 2b824e8096
Updated security readme (#4892) 
Update the security readme with a new GPG security key and some small
other changes.

Signed-off-by: BlackDex <black.dex@gmail.com>
2024-08-24 18:59:27 +02:00

2.9 KiB
Raw Permalink Blame History

Vaultwarden tries to prevent security issues but there could always slip something through. If you believe you've found a security issue in our application, 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.

In-scope

Exclusions

The following bug classes are out-of scope:

  • Bugs that are already reported on Vaultwarden's issue tracker (https://github.com/dani-garcia/vaultwarden/issues)
  • Bugs that are not part of Vaultwarden, like on the the web-vault or mobile and desktop clients. These issues need to be reported in the respective project issue tracker at https://github.com/bitwarden to which we are not associated
  • Issues in an upstream software dependency (ex: Rust, or External Libraries) which are already reported to the upstream maintainer
  • Attacks requiring physical access to a user's device
  • Issues related to software or protocols not under Vaultwarden's control
  • Vulnerabilities in outdated versions of Vaultwarden
  • Missing security best practices that do not directly lead to a vulnerability (You may still report them as a normal issue)
  • 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
  • Spamming
  • Social engineering (including phishing) of Vaultwarden developers, contributors or users

Thank you for helping keep Vaultwarden and our users safe!

How to contact us