Report a vulnerability

CORSAIR works with the security community to find vulnerabilities and keep our customers and business safe. If you've found one, we want to hear about it.

// Program rules

  • Provide detailed reports with reproducible steps. Reports that aren't detailed enough to reproduce may not be triaged.
  • Submit one vulnerability per report, unless you need to chain vulnerabilities to show impact.
  • When duplicates occur, we only triage the first report received, provided it can be fully reproduced.
  • Multiple vulnerabilities caused by one underlying issue count as one valid report.
  • Social engineering, including phishing, vishing, and smishing, is prohibited.
  • Make a good-faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our services. Only interact with accounts you own or with explicit permission from the account holder.

// Out of scope

When reporting, consider the attack scenario, exploitability, and security impact of the bug. These issues are out of scope.

Show the 18 out-of-scope issues
  • Clickjacking on pages with no sensitive actions
  • 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
  • Any activity that could lead to the disruption of our services (DoS)
  • Content spoofing and text injection issues without showing an attack vector or without being able to modify HTML/CSS
  • Rate limiting or brute force issues on non-authentication endpoints
  • Missing best practices in Content Security Policy
  • Missing HttpOnly or Secure flags on cookies
  • Missing email best practices (invalid, incomplete, or missing SPF, DKIM, or DMARC records)
  • Vulnerabilities only affecting users of outdated or unpatched browsers (less than two stable versions behind the latest released stable version)
  • Software version disclosure, banner identification issues, or descriptive error messages or headers (for example, stack traces or application or server errors)
  • Public zero-day vulnerabilities with an official patch less than one month old, which are assessed case by case
  • Tabnabbing
  • Open redirect, unless additional security impact can be demonstrated
  • Issues that require unlikely user interaction

// Disclosure

Don't discuss reported vulnerabilities, including resolved ones, outside this program without express consent from CORSAIR. Follow HackerOne's disclosure guidelines.

// 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.

// Submit a report

To stay anonymous, leave the email field blank. Add your email to receive status updates. Detailed, reproducible steps help us validate your report faster.

Form not loading? Open the form on HackerOne.

// Questions?

Please reach out to security@corsair.com.