Intercom

Description

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.

Targets

All other domains/end-points other than those listed in the targets section, are out of scope. Target info: Fin AI Agent: https://www.intercom.com/help/en/articles/7120684-fin-ai-agent-explained 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-app API Documentation: https://developers.intercom.com/ Most recent features added to the product: https://www.intercom.com/changes/en 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 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! Notes on Permission / Paywall Bypasses Intercom follows a shared security model. Intercom workspace owners are advised to exercise caution when inviting contributors to their workspaces. While Intercom provides various user permissions that can help restrict access to certain high-risk operations, these permissions serve as a secondary layer of defense. The primary safeguard is ensuring that invited users are trusted. Therefore: Permission Bypasses occurring within a single workspace will be assigned a priority of P3 or lower . A P3 priority will only be given to Permission Bypasses that have a significant impact on end-user privacy or data, typically involving access to conversation data and/or users' PII or profile information. All other Permission Bypasses , excluding Paywall Bypasses, will be categorized as P5 Informational for triage and rewards. A Paywall Bypass refers to a bug that allows Intercom users to access features that would normally require an upgraded paid plan. These reports are not accepted, as they do not impact our users. The guidelines outlined above are intended to set expectations for researchers. However, we reserve the right to make exceptions when evaluating specific reports—we may adjust the priority up or down or even reject a report entirely. That said, in practice, we have consistently adhered to these rules over many years of handling Permission Bypass reports. As a result, deviations from these guidelines in triage outcomes should be considered highly unusual. How to sign up for an Intercom account / app: Intercom currently offers two primary trial paths, both of which create Intercom workspaces that are in scope for this program: Fin AI Agent on your current helpdesk The Intercom Suite To sign up: Go to https://app.intercom.com/a/start?security_researcher=true Use your Bugcrowd email address ([email protected]). Failure to do so will result in your account being terminated with no reward granted for any valid found bug. To add a teammate, go to https://app.intercom.com/a/apps/_/settings/teammates/invite and add their email address to issue an invite. Focus Areas: OWASP Top 10 for LLMs and Gen AI Apps Cross site scripting (XSS), including those blocked by our Content Security Policy (CSP) Cross site request forgery on critical actions 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.