Submit bug reportA fundamentally new way to communicate with your customers. Intercom is one place for every team in an internet business to communicate with customers, personally, at scale—on your website, inside web and mobile apps, and by email.
We appreciate all security concerns brought forth and are constantly striving to keep on top of the latest threats. Being pro-active rather than re-active to emerging security issues is a fundamental belief at Intercom. Every day new security issues and attack vectors are created. Intercom strives to keep abreast on the latest state-of-the-art security developments by working with security researchers and companies. We appreciate the community's efforts in creating a more secure world.
Rewards:
Intercom will rely on the Bugcrowd Vulnerability Rating Taxonomy for prioritization of findings- but reserve the right to either downgrade or upgrade findings’ severity based on the criticality of their underlying risk to Intercom. Appropriate payouts will then be awarded accordingly. Any downgraded submission with come with a full and detailed explanation.
Target info:
Inbox App Release Information:
https://www.intercom.com/blog/videos/announcing-inbox-apps/iOS IPA and Android SDK available here:
https://docs.intercom.com/install-on-your-product-or-site/quick-install/install-and-configure-intercom-on-your-mobile-appAPI Documentation:
https://developers.intercom.com/The target URLs are the same as those used by our real customers, please keep this in mind and act accordingly.
Avoid creating a nuisance to Intercom's customers as much as possible. This includes among other things testing Messenger security by sending payloads to real customers; instead set up your own Intercom account, and your own Messenger installation. up (removing those posts) should be done.
Automated vulnerability scans are strictly prohibited.
No attacks against Intercom's existing user base.
No DDoS attacks
We currently don't accept Paywall Bypass attacks. This is a temporary measure, and we will most likely move them back in scope in the future.
This is Intercom's primary production environment. We accept valid PoCs of app-level Denial of Service vulnerabilities but PoCs that intentionally stress or risks the availability of our services will be considered an abuse
Create your own Intercom accounts (likely two, at least - for cross-org testing) to perform research against this app.
Do not create more than 4 apps as part of your testing. Failure to comply may result in your account being blacklisted, thanks!
Focus Areas:
Cross site request forgery on critical actions
Cross site scripting (XSS), including those blocked by our Content Security Policy (CSP)
Remote code execution / shell injection
Authentication bypass
SQL injection
Insecure direct object references
Testing is only authorized on the targets listed as In-Scope. Any domain/property of Intercom not listed in the targets section is out of scope. This includes any/all subdomains not listed above. If you happen to identify a security vulnerability on a target that is not in-scope, but that demonstrably belongs to Intercom, it may be reported to this program, and is appreciated - but will ultimately be marked as 'not applicable' and will not be eligible for monetary or points-based compensation.
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 email support@bugcrowd.com. 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.
