Asana

  • $100 – $6,500 per vulnerability
  • Partial safe harbor

Program stats

  • Vulnerabilities rewarded 151
  • Validation within 4 days 75% of submissions are accepted or rejected within 4 days
  • Average payout $427.50 within the last 3 months

Latest hall of famers

Recently joined this program

No technology is perfect and Asana believes that working with skilled security researchers across the globe is crucial in identifying weaknesses in any technology. We are excited for you to participate as a security researcher in order to identify weaknesses. If you believe you've found a security issue, we encourage you to notify us. We welcome working with you to resolve the issue promptly.

Ratings/Rewards:

For the initial prioritization/rating of findings, this program will use the Bugcrowd Vulnerability Rating Taxonomy. However, it is important to note that in some cases a vulnerability priority will be modified due to its likelihood or impact. In any instance where an issue is downgraded, a full, detailed explanation will be provided to the researcher - along with the opportunity to appeal, and make a case for a higher priority.

Likelihood = How likely this particular vulnerability is to be uncovered and exploited by an attacker?
Impact = Technical impact + Business impact. The first is the “technical impact” on the application, the data it uses, and the functions it provides. The other is the “business impact” on the business and company operating the application. See OWASP methodology for risk rating as a reference.

Asana uses a nonce based CSP policy. If you discover an XSS vulnerability that you cannot exploit due to the CSP policy, but would at least be a P4 without the CSP policy present, we will reward that vulnerability as if it was a P4.

Please also include the following information in your submission (if applicable):

Domain Type (organization/workspace)
Domain ID(s) used
Domain Tier (free/premium/business/enterprise)
Attacker membership level(s)
Victim membership level(s)
Security Impact
Emails of accounts used for testing

Special note on prompt injection

We will consider submissions of this type if you can manipulate AI to have a measurable security impact to Asana, not just manipulating the AI model.

Scope and rewards

Program rules

This program follows Bugcrowd’s standard disclosure terms.

For any testing issues (such as broken credentials, inaccessible application, or Bugcrowd Ninja email problems), please submit through the Bugcrowd Support Portal. We will address your issue as soon as possible.

This program does not offer financial or point-based rewards for P5 — Informational findings. Learn more about Bugcrowd’s VRT.