Bug Bounty Program / Reporting Security Issues

No technology is perfect, and Showmax believes that working with skilled security researchers across the globe is crucial in identifying weaknesses in any technology. If you believe you’ve found a security issue in our product or service, we encourage you to notify us. We welcome working with you to resolve the issue promptly.

Disclosure Policy and Rules of Participation

  • Let us know as soon as possible upon discovery of a potential security issue, and we’ll make every effort to quickly resolve the issue.
  • Provide us a reasonable amount of time to resolve the issue before any disclosure to the public or a third-party.
  • Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service. Only interact with accounts you own or with explicit permission of the account holder.
  • You may only test against accounts you have created.
  • You must not attempt to gain access to, or interact with, any accounts other than those created by you
  • We cannot whitelist IP addresses, nor allow VPN access.
  • We are not releasing vouchers for test purposes.
  • Always include as much as details as reasonable. If reporting incorrect behaviour of API, always include relevant part of response (for example headers). When API is involved always include our tracing header Showmax-Request-Id.
  • Rules for reporting must be followed
  • This program is not open to minors, individuals on sanctions lists or individuals in countries on sanctions lists
  • Showmax reserves the right to modify the rules for this program or deem any submissions invalid at any time. Showmax may cancel the Bug Bounty program without notice at any time.

Please use HackerOne platform. If you feel the email/report should be encrypted, please use our PGP key.

Thank you for helping keep Showmax and our users safe!

Eligibility

Scope of bug hunting project is limited to services directly provided by Showmax. Such as web, api, native applications. Please note that bugs in third-party components only qualify if you can prove that they can be used to successfully attack Showmax.

Eligible services/products:

Out of scope: We don’t consider 3rd party services as eligible for this program (for example https://help.showmax.com which is hosted by 3rd party). We also consider other service domains (e.g. showmax.io or showmax.cc) out of scope by default. But if you think that you have discovered something important, please report it. We may consider your report and award bounty even for these domains, if we believe, that your report has a significant value.

Also be aware about API version and platform being part of the API url as /v{api_major_version}.{api_minor_version}/{platform}/. For example there is probably very little value in reporting separate issues against api.showmax.com/v42.0/website/some_endpoint and api.showmax.com/v42.2/website/some_endpoint or api.showmax.com/v42.0/ios/some_endpoint.

Vulnerability Categories We Encourage

We are primarily interested in hearing about the following vulnerability categories:

  • Authentication related issues (e.g. authentication bypass for login to My Account)
  • Authorisation related issues (e.g. authorisation bypass for asset playback)
  • SQL Injection (SQLi)
  • Cross Site Scripting (XSS)
  • Data Exposure
  • Redirection Attacks
  • Remote Code Execution
  • Particularly clever vulnerabilities or unique issues that do not fall into explicit categories

Out of Scope Vulnerability Categories

The following vulnerability categories are considered out of scope of our responsible disclosure program and will not be eligible for credit and/or bounty.

  • SSL vulnerabilities related to configuration or version
  • Denial of Service (DoS). There is also rate-limiting functionality on our service, that will kick in after abusive amount of requests is made. There is not need for you to test it and it also has different thresholds for different urls (e.g. much lower for auth related endpoints).
  • User enumeration
  • Password policies/2FA (we not trying to build bank here)
  • Brute forcing
  • Secure flag not set on non-sensitive cookies
  • HTTPOnly flag not set on non-sensitive cookies as some cookies needs to be readable by other parts of our platform (e.g. showmax_auth accessed by JavaScript application)
  • Logout Cross Site Request Forgery (CSRF)
  • Handling of CSRF token (it is tied to particular app session cookie)
  • HTTP access control (CORS)
  • Self-XSS
  • Cookie showmax_oauth not having a Secure flag set
  • Certain services passing access_token in params
  • Issues only present in old browsers/old plugins/end-of-life software browsers
  • HTTP TRACE method enabled
  • Vulnerability reports related to the reported version numbers of web servers, services, or frameworks
  • Clickjacking on pages without authentication and/or sensitive state changes
  • Missing Content-Security-Policy (CSP)
  • Open ports for services on the servers (e.g. open ssh)
  • Reports related to password reset token handling, its immediate invalidation etc.
  • Vulnerability reports that require a large amount of user cooperation to perform unlikely or unreasonable actions which would be more symptomatic of a social engineering or phishing attack and not an application vulnerability (e.g. disabling browser security features, sending the attacker critical information to complete the attack, guiding the user through a particular flow and requiring them to enter malicious code themselves, etc.)
  • Any physical attempts against Showmax property or data centers
  • Social engineering (including phishing) of Showmax staff or contractors
  • Spamming
  • Email routing related issues, such as SPF, DKIM or DMARC configuration
  • Bruteforce Amplification Attack via https://blog.showmax.com/xmlrpc.php

Payouts (on HackerOne)

Our vulnerability-reward payouts will go up to 1,000 USD for the most impactful exploits. If we accept your report, our minimum bounty is 100 USD. We are able to provide bounties only via HackerOne platform.

Indemnification

Showmax will not pursue legal action against security researchers who follow the guidelines outlined in this document and responsibly disclose vulnerabilities to us.

Participating Security Researchers

Showmax would like to thank the following researchers for participating in our responsible disclosure program. They are listed in alphabetical order.

2018

Reda El Hachloufi @666reda
Aman Mahendra @amanmahendra
@black-shadow
Andrea @bocc
Codarren Velvindron @codarren
Shreyas Jadhav @cselyf
@dotx
gujjuboy0x00 @gujjuboy10x00
Sergey Kashatov @iframe
insomniac @insomniac
irmiaw @irmiaw
@japz
hi @jishnuk
@karthic
Kunal @kunal94
Liam Somerville @lsinfosec
Michał Muszalski @mmuszalski
Monish @monish
Mostafa Mamdoh @mostafamamdoh
Juho Myllys @muon4
Nightwatch Cybersecurity @nightwatch-cybersecurity
What's king to a god ? @ninja0x01
oldhacker @oldhacker
Kenneth A. Davis @poesed86
Pratik Bhoir @pr4tik_9007
Prafull Pansare @prafull_pansare
vasateja @rahulztez
Nikita Tikhomirov (Pentest Generation) @redfault
reydd @reymark_divino
hacked @rogov
Security killer @rootbd
sachin kumar @sachin_kumar19
Shunmugha Sundaram @shamrocksu88
Sherwyn Moodley @sherwyn
static21 @static21
Suhas @suhas_gaikwad
Bilal Rizwan @th3_3inst3in
CongRong @tr3jer
@urztruzchitrz
Veena @veena
Jack @ven0ms
Mohammed Israil @villagelad
joël aviad ossi @websecnl
Whitehat_Hacker @whitehat_hacker
Aditya Dixit @z0mb13

2017

addd @add12344441
@alpha66
Bugdiscloseguys @bugdiscloseguys
user[username] @daniyal_nasir
Dawid Czagan @dawidczagan
Md. Nur A Alam Dipu @depu1994
Sahil Ahamad @ehsahil
@exception
Brian Carpenter @geeknik
Gabe Pike @gpike
Mehdi Hashemi @hat_mast3r
0xCiph3r00t @im_ciph3r00t
Jigar Thakkar @jigarthakkar39
Mohammad Aman KHAN @leet-boy
Luciano Corsalini @lucio
Muhammad Abdullah @mahitman
Mark Litchfield @mlitchfield
Nightwatch Cybersecurity @nightwatch-cybersecurity
Black Ashes @nullelite
Paresh parmar @paresh_parmar
Peter 🎩🎩🎩🎩 @peter-676
Sahil Saif @sahilsaif Top Hacker
Sergii Sizov @sergiisizov
SuperBoy @sup3r-b0y
AMT @temmyscript
Eric @todayisnew
yappare @yappare

Cover image by Negative Space. It features Prague Castle Guards.