Responsible Disclosure Policy

HackerOne

https://hackerone.com/b21888db-e0d1-48cd-b61b-55aaa96600d4/embedded_submissions/new

Response Targets

Disclosure Policy

• As this is a private program, please do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express consent from the organization.

• Follow HackerOne's disclosure guidelines.

Program Rules

• Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue, the issue will not be eligible for a reward.

• Submit one vulnerability per-report, unless you need to chain vulnerabilities to provide impact.

• When duplicates occur, we only award the first report that was received (provided that it can be fully reproduced).

• Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.

• Social engineering (e.g. phishing, vishing, smishing) is prohibited.

• 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 the explicit permission of the account holder.

• Reports that cover more than one asset in scope will be paid out once at the highest paying in scope asset category.

In Scope Targets

• notion.so Web App

• notion.so backend APIs and infrastructure

• Notion iOS app

• Notion Android app

• Notion desktop executable (versions on notion.so/desktop)

Out of Scope Vulnerabilities

When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug.

The following potential issues are not considered in scope:

• Social engineering or phishing of Notion employees or contractors

• Any attacks against Notion's physical property or data centers

• Any attacks against Notion's users

• Use of automated scanning tools

• Lack of rate limiting on any resources

• Password policy issues, including lack of upper limit on passwords

• HTTP 404 or other error codes and pages

• Banner or version disclosure of any kind

• Presence of common public files, such as robots.txt or files in the .well-known directory

• Self-XSS issues

• Spamming

• Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)

• Clickjacking on pages with no sensitive actions

• Clickjacking issues, unless an exploit showing account takeover or disclosure of sensitive resources is provided

• Cross-Site Request Forgery (CSRF) / Server-Side Request Forgery (SSRF) on unauthenticated forms or forms with no sensitive actions

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

• Previously known vulnerable libraries without a working Proof of Concept.

• Comma Separated Values (CSV) injection without demonstrating a vulnerability.

• Missing best practices in SSL/TLS configuration.

• 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

• Missing best practices in Content Security Policy

• Missing HttpOnly or Secure flags on cookies

• Missing security headers which don’t directly lead to a vulnerability or account compromise

• Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version]

• Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors)

• Public Zero-day vulnerabilities that have had an official patch for less than 1 month will be awarded on a case by case basis

• Tabnabbing

• Open redirect - unless an additional security impact can be demonstrated

• Notion hosting malware / Spam / Phishing websites

• Issues that require unlikely user interaction

• Obtaining access to a paid feature of a higher level plan

• Revealing identity information on published *.notion.site pages

• Expected behaviors as described in the Notion Documentation

• Javascript execution on file.notion.so and notion-static.com is expected. To be considered in scope, you will need to demonstrate how it harms users on in-scope assets.

• For Notion’s AI, engineered prompts to evoke inappropriate responses from the AI is out of scope.

• Bypasses of lock features on page and database views

Safe Harbor