Details

Mux is an API driven platform for developers to build amazing video experiences into their websites or apps.

We work hard to ensure Mux is a safe and secure environment for our customers and their viewers. We welcome and reward vulnerability reports from the security community, and run a private bug bounty program on HackerOne.

To avoid duplicate or out of scope reports, we very strongly recommend that you join or program directly on HackerOne so that you can read the full Policy before submission. For an invite, please drop us an email with your HackerOne username to [email protected].

You may want to read more about Mux, and how to get started on the platform before starting to find vulnerabilities.

You can read more about our Video product here: https://mux.com/video https://docs.mux.com/docs/video

You can read more about our Data product here: https://mux.com/data https://docs.mux.com/docs/data

Disclosure Policy

Please do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express consent from Mux.
Follow HackerOne's disclosure guidelines.

Program Rules

Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue, the issue will not be eligible for a reward.
Vulnerabilities must demonstrate a path to exploitation. Security related bugs or misconfigurations are not considered valid unless they create an exploit.
Submit one vulnerability per-report, unless you need to chain vulnerabilities to provide impact.
When duplicates occur, we only award the first report that was received (provided that it can be fully reproduced).
Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.
Social engineering (e.g. phishing, vishing, smishing) is prohibited.
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 the explicit permission of the account holder. Mux allows free account signups that can be used to demonstrate vulnerabilities. Mux can provide up/down graded accounts upon request if needed to demonstrate vulnerability.
Don't use automated tools or scanners. Reports will be closed as N/A.

Rewards

Our rewards are based on severity per CVSS (the Common Vulnerability Scoring Standard), and are disclosed in our private bounty program. If you wish to review our rewards before submitting, please request an invite to our private program by emailing [email protected].

Out of scope vulnerabilities

When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug. The following issues are considered out of scope:

Any form of vulnerability caused by sessions not being ended on logout or password change
Any form of vulnerability caused by session reuse
Any from of Clickjacking vulnerability
Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions
Attacks requiring MITM or physical access to a user's device.
Previously known vulnerable libraries without a working Proof of Concept.
Comma Separated Values (CSV) injection without demonstrating a vulnerability.
Missing best practices in SSL/TLS configuration, including outdated TLS versions.
Any activity that could lead to the disruption of our service (DoS).
Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
Rate limiting or bruteforce issues on non-authentication endpoints
Missing rate limits, unless it can lead to account takeover
Presence of autocomplete attribute on web forms
Missing best practices in Content Security Policy.
Missing HttpOnly or Secure flags on cookies
Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)
Vulnerabilities only affecting users of outdated or unpatched browsers (Less than 2 stable versions behind the latest released stable version)
Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors).
Public Zero-day vulnerabilities that have had an official patch for less than 1 month will be awarded on a case by case basis.
Self-XSS (XSS exploits that cannot maliciously affect users besides yourself)
Tabnabbing
Open redirect - unless an additional security impact can be demonstrated
Issues that require unlikely user interaction
Information leakage to a trusted Mux third party, EG: Hubspot.

Safe Harbor

Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you. If legal action is initiated by a third party against you in connection with activities conducted under this policy, we will take steps to make it known that your actions were conducted in compliance with this policy.

Thank you for helping keep Mux and our users safe!

Program Rules

Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue, the issue will not be eligible for a reward.

Vulnerabilities must demonstrate a path to exploitation. Security related bugs or misconfigurations are not considered valid unless they create an exploit.

Submit one vulnerability per-report, unless you need to chain vulnerabilities to provide impact.

When duplicates occur, we only award the first report that was received (provided that it can be fully reproduced).

Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.

Social engineering (e.g. phishing, vishing, smishing) is prohibited.

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 the explicit permission of the account holder. Mux allows free account signups that can be used to demonstrate vulnerabilities. Mux can provide up/down graded accounts upon request if needed to demonstrate vulnerability.

Don't use automated tools or scanners. Reports will be closed as N/A.

Out of scope vulnerabilities

When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug. The following issues are considered out of scope:

Any form of vulnerability caused by sessions not being ended on logout or password change

Any form of vulnerability caused by session reuse

Any from of Clickjacking vulnerability

Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions

Attacks requiring MITM or physical access to a user's device.

Previously known vulnerable libraries without a working Proof of Concept.

Comma Separated Values (CSV) injection without demonstrating a vulnerability.

Missing best practices in SSL/TLS configuration, including outdated TLS versions.

Any activity that could lead to the disruption of our service (DoS).

Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS

Rate limiting or bruteforce issues on non-authentication endpoints

Missing rate limits, unless it can lead to account takeover

Presence of autocomplete attribute on web forms

Missing best practices in Content Security Policy.

Missing HttpOnly or Secure flags on cookies

Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)

Vulnerabilities only affecting users of outdated or unpatched browsers (Less than 2 stable versions behind the latest released stable version)

Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors).

Public Zero-day vulnerabilities that have had an official patch for less than 1 month will be awarded on a case by case basis.

Self-XSS (XSS exploits that cannot maliciously affect users besides yourself)

Tabnabbing

Open redirect - unless an additional security impact can be demonstrated

Issues that require unlikely user interaction

Information leakage to a trusted Mux third party, EG: Hubspot.

Safe Harbor

Thank you for helping keep Mux and our users safe!