Skip to content
bugbounty.fyi
Get paid to secure open source 475 paid open-source programs on Sorona, up to $1M Perk Low bugs: $100 or 1 mo Claude Max

Also on Patchstack. All 476 paid open-source programs

Try

Highest paying Newly launched Paid without KYC Full safe harbor
All results

About this site

Asana

Bug bounty on Self-hosted asana.com

Accepting reports Full safe harbor
Go to program Website
Top reward
$6,500
Top severity paid
Critical
Assets in scope
11
Public CVEs
2
Last change
No changes yet

At a glance

What to know before you start testing.

Pays up to $6,500
for critical bugs, from $100.
Report by email
[email protected]
Full safe harbor
Good-faith research is authorised; no legal action.
Publish after a fix
Coordinate the timing with the company.

Rewards

What the company's own policy page says it pays.

Severity Reward
Critical $6,500 from $2,500
High $2,500 from $1,000
Medium $1,000 from $500
Low $500 from $100
Top reward
$6,500 P1 $ 2500 – $ 6500
Lowest reward
$100 P4 $ 100 – $ 500
Safe harbor
Full Authorized in accordance with the Computer Fraud and Abuse Act (CFAA) (and/or similar state laws), and we will not initiate or support legal action against you for accidental, good faith violations of this policy;
Hall of fame
Yes Latest hall of famers

Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original

Scope

11 assets you may test, 6 excluded.

Web 4

  • https://app.asana.com
  • https://*.asana.biz
  • https://asana.com
  • https://form.asana.com

Domains 2

  • asana.biz
  • asana.plus

Wildcard domains 2

  • *.app.asana.com
  • *.asana.plus

Android apps 1

  • Asana Android app

Desktop and binaries 1

  • Asana Desktop App

iOS apps 1

  • Asana iOS app
Out of scope (6)
  • asana.okta.com
  • assets.asana.biz
  • Forms that you do not own
  • jira*.integrations.asana.plus
  • Other subdomains of asana.com
  • Social engineering against Asana Support or Asana Employees

Rules

What the policy asks of you, and the bug types it won't reward, quoted from Asana's policy. "We" in these lines means the program, not this site.

While testing

  • Testing is only authorized on the targets listed as In-Scope.
  • If you find credentials, including but not limited to Asana logins, Okta logins, etc please report them but DO NOT attempt to log in.
  • Do not access or manipulate data outside of domains that you control (including but not limited to customer data).
  • Intentional access to data or information not belonging to you beyond the minimum necessary to demonstrate the vulnerability.
  • Any testing involving making repetitive network requests. This includes testing for denial of service attacks and testing to see if rate limits are properly in place.
  • Submitting any form on form.asana.com or form-beta.asana.biz that you did not create yourself.
  • Please self sign up for a free account using your @bugcrowdninja.com email address at https://asana.com/create-account .
  • Any activity that could lead to the disruption of our service (DDoS/DoS)

Not accepted

  • HTTP 404 codes/pages or other HTTP non-200 codes/pages.
  • Fingerprinting / banner disclosure on common/public services.
  • Disclosure of known public files or directories, (e.g. robots.txt).
  • Clickjacking and issues only exploitable through clickjacking.
  • Security best practices without evidence of security impact or exploitation
  • Weak login/signup without evidence of security impact or exploitation
  • Weak password policy without demonstrated impact or exploitation
  • Cookie issues without evidence of security impact or exploitation
  • Lack of Secure/HTTPOnly flags on non-sensitive Cookies.
  • Missing HTTP security headers
  • Descriptive error messages (e.g. Stack Traces, application or server errors).
  • EXIF data not being stripped from files or attachments.
  • Attacks that aim to destroy or corrupt data not belonging to you.
  • Attacks attempting to extend trial licenses.
  • Rate limiting or brute force issues
  • Missing best practices in Content Security Policy.
  • Missing HttpOnly or Secure flags on cookies
  • Reports from automated scanners
  • User/email enumeration
  • Dependency confusion
  • Open redirect without demonstrated security impact
  • Self-XSS without demonstrated security impact
  • Blind SSRF without demonstrated security impact.
  • Tabnabbing
  • Issues that require unlikely user interaction

Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original

Changes

Tracked since 11 Nov 2026. Last checked 5 hours ago.

No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.

Public CVEs

Published vulnerabilities in this vendor's products, from the NVD.

Search NVD
CVESeverityPublished
CVE-2023-49314 High 7.8 28 Nov 2023
CVE-2022-26877 Medium 6.5 9 Apr 2022