Twilio

Ensuring the security and integrity of the Twilio platform is critical to the service we provide to our customers. We are committed to providing a secure product and appreciate help from the community in responsibly identifying ways for us to improve Twilio. We will make an effort to respond as fast as possible.

Rules of Engagement

• Bounties are awarded differently per product (see below for more details on payouts).
• Network Level DDoS/DoS attacks are forbidden. Application volumetric DDoS/DoS attacks are forbidden, if you find a request that takes too long to answer report it, please do not try to DoS the service.
• Interacting with real customers is forbidden.
• To prevent being locked out please throttle automated testing
• Please note, if you think you have found a problem but cannot prove it without accessing Twilio's Internal Systems, please submit your finding and we'll be happy to work with you for validation.
• Please ensure that you use your @bugcrowdninja.com email address when creating accounts and testing
• While creating any assets please use bugcrowd-<your email>-<random string>
• Any POCs created as part of testing (such as npm packages) should follow the convention: twilio-bugcrowd-poc-<additional-string> and they should be deleted once the submission is triaged

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.

Rewards:

Category	Primary	Secondary	Other
P1	$3,000 - $8,000	$500 - $1,000	$100 - $200
P2	$1000 - $2,500	$200 - $500	Kudos -$100
P3	$200 - $400	$100 - $200	N/A
P4	$100 - $150	Kudos	N/A

Target Overview

Primary Targets

• Twilio Console
• Twilio Core Products
• Twilio API’s
• Twilio WebRTC Client
• Twilio SIP endpoints
• Twilio WebSockets (tsock.*.twilio.com)

Secondary Targets

• Twilio Developer Docs
• Twilio CDNs(static*.twilio.com)
• Twilio Blog
• Twilio Partner

Other Targets

Any host/web property verified to be owned by Twilio (domains/IP space/etc.) but not listed in Primary or Secondary targets and not listed as Out of Scope.

NOTE: If a submission falls under Secondary or Other targets, and has a significant impact, bounty may be increased at Twilio’s discretion.

Focus Areas

Core Twilio Products
Twilio Console
Twilio APIs
SIP
Video
Twilio WebRTC Client

Excluded Submission Types

• "Session too long," password reset/change logout or other intended business functionality
• All Wordpress-related findings
• Flash findings that require Flash to be enabled
• OpenVBX related findings
• Subdomain takeovers of TLD's used for demo or test purposes [such as companyfoo.com]
• Cookie valid after password change/reset
• Forgot password auto-login
• Denial of service or rate limiting issues
• Resource Exhaustion attacks
• Login or Forgot Password page brute force and account lockout not enforced
• Non-existent or weak captcha / captcha bypass
• Email validation not enforced
• Presence of application or web browser ‘autocomplete’ or ‘save password’ functionality.
• SSL/TLS Issues such as:BEAST, BREACH, SSL insecure cipher suites enabled.
• S3 bucket takeover from Twilio docs or Twilio public GitHub repos.
• Subdomain takeover for Sendgrid subdomains
• Vulnerabilities that are limited to older/unsupported browsers
• Known vulnerabilities in libraries used by Twilio, usage of an outdated third party library (e.g. jQuery, Apache etc) unless you can prove exploitability.

Public Disclosure

Twilio does not permit public disclosure at this point in time. Exceptions will be made when the Twilio Security team decides to publish a CVE for vulnerabilities identified in desktop apps, mobile apps and SDKs based on the severity of the identified issue. Incase a CVE is published, we will reach out to the researcher for permission before mentioning them. The vulnerability will be mentioned here: https://www.twilio.com/changelog

Twilio Safe Harbor

We will not pursue civil action or initiate a complaint to law enforcement for accidental, good faith violations of this policy. We consider activities conducted consistent with this policy to constitute “authorized” conduct under the Computer Fraud and Abuse Act. To the extent your activities are inconsistent with certain restrictions in our Acceptable Use Policy, we waive those restrictions for the limited purpose of permitting security research under this policy. We will not bring a DMCA claim against you for circumventing the technological measures we have used to protect the applications in scope.
If legal action is initiated by a third party against you and you have complied with Twilio's bug bounty policy, Twilio will take steps to make it known that your actions were conducted in compliance with this policy.
Please submit a BugCrowd report to us before engaging in conduct that may be inconsistent with or unaddressed by this policy