Description

CM.com is a listed company that provides Conversational Commerce services from its privately owned cloud platform with 100% in-house developed software. We continuously develop our private cloud platform, shaping the future of Conversational Commerce. CM.com’s customer base is spread over 118 countries, generating messages to more than 220 destinations. Customers include Tier 1 enterprises, government agencies, as well as small and medium sized enterprises.

Bounties
Low
Medium
High
Critical
Exceptional
Tier 2
€50
€250
€600
€1,000
€2,500
€50 - €2,500
Tier 3
€25
€125
€250
€375
€500
€25 - €500
Rules of engagement
Required
Not applicable
max. 2 requests/sec
Not applicable

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 😉)
Domains

*.cmtickets.com

Tier 2
URL

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})

api.cm.com

Tier 2
URL

api.cmtelecom.com

Tier 2
URL

Some of the applications that are in our scope use our old api.
If you find a bug on this api and it is from a product that is in scope, it is valid.

login.cm.com

Tier 2
URL

www.cm.com/[locale]/app/*

Tier 2
URL

www.cm.com/[locale]/register

Tier 2
URL

www.cm.com

Tier 3
URL

*.cm.com

No Bounty
URL
In scope

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

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

Out of scope Domains

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

Application

  • 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. We are aware of this issue and are working on solving it platform wide.
  • CSV Injection
  • Sessions not being invalidated (logout, enabling 2FA, ..)
  • Hyperlink injection/takeovers
  • Mixed content type issues
  • Cross-domain referer leakage
  • Anything related to email spoofing, SPF, DMARC or DKIM
  • Content injection
  • Username / email enumeration
  • E-mail bombing
  • HTTP Request smuggling without any proven impact
  • Homograph attacks
  • XMLRPC enabled
  • Banner grabbing / Version disclosure
  • Open ports without an accompanying proof-of-concept demonstrating vulnerability
  • Weak SSL configurations and SSL/TLS scan reports
  • Not stripping metadata of images
  • Disclosing API keys without proven impact
  • Same-site scripting
  • Subdomain takeover without taken over the subdomain
  • Arbitrary file upload without proof of the existence of the uploaded file
  • Blind SSRF without proven business impact (DNS pingback only is not sufficient)
  • Disclosed and/or misconfigured Google API key (including maps)
  • 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, may be excluded or be lowered in severity
  • Spam, social engineering and physical intrusion
  • DoS/DDoS attacks or brute force attacks.
  • Vulnerabilities that are limited to non-current browsers (older than 3 versions) will not be accepted
  • 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
Severity assessment

This programs follows Intigriti's contextual CVSS standard.

FAQ

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.

All aboard!
Please log in or sign up on the platform

For obvious reasons we can only allow submissions or applications for our program with a valid intigriti account.

It will only take 2 minutes to create a new one or even less to log in with an existing account, so don't hesitate and let's get started. We would be thrilled to have you as part of our community.

Researchers
last contributors
logo
logo
logo
logo
logo
logo
leaderboard
logo
logo
logo
logo
logo
logo
Overall stats
submissions received
220
average payout
€291
accepted submissions
80
total payouts
€15,885
Last 90 day response times
avg. time first response
< 2 days
avg. time to decide
+3 weeks
avg. time to triage
< 4 days
Activity
5/14
logo
created a submission
5/13
CM.com
closed a submission
5/13
logo
created a submission
5/10
CM.com
closed a submission
5/10
CM.com
closed a submission
5/9
CM.com
accepted a submission
5/9
CM.com
accepted a submission
5/8
logo
created a submission
5/6
CM.com
accepted a submission
5/4
CM.com
closed a submission