Security

Vulnerability Disclosure Policy

Introduction

Raspberry Pi Foundation welcomes feedback from security researchers and the general public to help improve our security. If you believe you have discovered a vulnerability, privacy issue, exposed data, or other security issues in any of our assets, we want to hear from you. This policy outlines steps for reporting vulnerabilities to us, what we expect, what you can expect from us.

Please note this is not a bug bounty program, and we do not offer rewards for disclosures.

Systems in Scope

This policy applies to any digital assets owned, operated, or maintained by Raspberry Pi Foundation, including our domains (e.g. *.raspberrypi.org), APIs, web apps, hosted services, and open source repositories under the Raspberry Pi Foundation GitHub organisation.

Out of Scope

  • Assets or other equipment owned, operated, or maintained by Raspberry Pi Holdings PLC, such as Raspberry Pi hardware and raspberrypi.com. Please visit https://www.raspberrypi.com/contact/security if that describes your disclosure.
  • Assets or other equipment not owned by parties participating in this policy.

Vulnerabilities discovered or suspected in out-of-scope systems should be reported to the appropriate vendor or applicable authority.

Our Commitments

When working with us, according to this policy, you can expect us to:

  • Respond to plausible reports within 5 business days, and work with you to understand and validate your report;
  • Strive to keep you informed about the progress of a vulnerability as it is processed; and
  • Work to remediate discovered vulnerabilities in a timely manner, within our operational constraints.

Our Expectations

In participating in our vulnerability disclosure program in good faith, we ask that you:

  • Play by the rules, including following this policy and any other relevant agreements. If there is any inconsistency between this policy and any other applicable terms, the terms of this policy will prevail;
  • Report any vulnerability you’ve discovered promptly;
  • Avoid violating the privacy of others, disrupting our systems, destroying data, and/or harming user experience;
  • Do not engage in any form of social engineering (e.g. phishing), denial of service attacks, or any action that could degrade services for real users;
  • Avoid high-volume or aggressive scanning tools that may degrade service availability;
  • Use only the Official Channels to discuss vulnerability information with us;
  • Provide us a reasonable amount of time (at least 90 days from the initial report) to resolve the issue before you disclose it publicly;
  • Perform testing only on in-scope systems, and respect systems and activities which are out-of-scope;
  • Limit the amount of data you access to the minimum required for effectively demonstrating a Proof of Concept; and cease testing and submit a report immediately if you encounter any user data during testing, such as Personally Identifiable Information (PII), Personal Healthcare Information (PHI), credit card data, or proprietary information;
  • Only interact with test accounts you own or with explicit permission from the account holder; and
  • Do not engage in extortion.

Official Channels

Please report security issues via one of these official channels, providing all relevant information:

  • Email: security@raspberrypi.org
  • The Keybase app: our username is rpfwebteam (sends end-to-end encrypted messages)

Reports may be encrypted at your discretion. You can send us an encrypted message on Keybase, or alternatively encrypt text using Keybase’s web interface (or any other means using our PGP key), then paste it into an email.

The more details you provide, the easier it will be for us to triage and fix the issue.