By participating in this program, you agree to:

• Respect the Community Code of Conduct
• Respect the Terms and Conditions
• Respect the scope of the program
• Not discuss or disclose vulnerability information without prior written consent (including PoC’s on YouTube and Vimeo)
• Please do not use automatic scanners -be creative and do it yourself! We cannot accept any submissions found by using automatic scanners. Scanners also won't improve your skills, and can cause a high server load (we'd like to put our time in thanking researchers rather than blocking their IP's 😉)

Important! Please use your @intigriti.me accounts, otherwise it is highly likely you will be blocked.

We are specifically looking for:

• leaking of personal data
• SQLi
• RCE

Please do not use the following methods:

• Bruteforce -> Password / Username bruteforce
• Directory / file / content enumeration: see rate limit guidelines

Our API's
You can use the platform or API's (docs) to use products.

New Application: Ticketing
How does this work?
Login to your account and go to https://www.cm.com/en-gb/app/ticketing/
From here you can create tickets and much more!
Make sure to take a look at the user-side as well (https://reserve.cmtickets.com/{GUID-OF-TICKET})

Out of scope Domains

• All domains that fall outside the scope that we listed.

Application

• API key disclosure without proven business impact
• Wordpress usernames disclosure
• Pre-Auth Account takeover/OAuth squatting
• Self-XSS that cannot be used to exploit other users
• Verbose messages/files/directory listings without disclosing any sensitive information
• CORS misconfiguration on non-sensitive endpoints
• Missing cookie flags
• Missing security headers
• Cross-site Request Forgery with no or low impact
• Presence of autocomplete attribute on web forms
• Reverse tabnabbing
• Bypassing rate-limits or the non-existence of rate-limits.
• Best practices violations (password complexity, expiration, re-use, etc.)
• Clickjacking without proven impact/unrealistic user interaction
• CSV Injection
• Sessions not being invalidated (logout, enabling 2FA, etc.)
• Tokens leaked to third parties
• Anything related to email spoofing, SPF, DMARC or DKIM
• Content injection without being able to modify the HTML
• Username/email enumeration
• Email bombing
• HTTP Request smuggling without any proven impact
• Homograph attacks
• XMLRPC enabled
• Banner grabbing/Version disclosure
• Not stripping metadata of files
• Same-site scripting
• Subdomain takeover without taking over the subdomain
• Arbitrary file upload without proof of the existence of the uploaded file
• Blind SSRF without proven business impact (pingbacks are not sufficient)
• Disclosed/misconfigured Google Maps API keys
• Host header injection without proven business impact

General

• In case that a reported vulnerability was already known to the company from their own tests, it will be flagged as a duplicate
• Theoretical security issues with no realistic exploit scenario(s) or attack surfaces, or issues that would require complex end user interactions to be exploited
• Spam, social engineering and physical intrusion
• DoS/DDoS attacks or brute force attacks
• Vulnerabilities that only work on software that no longer receive security updates
• Attacks requiring physical access to a victim's computer/device, man in the middle or compromised user accounts
• Recently discovered zero-day vulnerabilities found in in-scope assets within 14 days after the public release of a patch or mitigation may be reported, but are usually not eligible for a bounty
• Reports that state that software is out of date/vulnerable without a proof-of-concept

This programs follows Intigriti's contextual CVSS standard.

Where can we get credentials for the app?

You can self-register on the application but please don’t forget to use your @intigriti.me address.

I do not see the Ticketing application in the 9-dot-menu?

That's possible, you can find the appliction by going to https://www.cm.com/en-gb/app/ticketing/

How do I access the Mobile Marketing Cloud?

As of now we don’t proactively provide access to the MMC. You are allowed to request access, but the Security team has no influence in accepting your request.

Where do I find API documentation?

Taak a look at our developer portal!