Responsible Disclosure of Security Vulnerabilities
If you have discovered a vulnerability, we request that you responsibly disclose the vulnerability to our security team by taking the following steps:
- Do not attempt to exploit the vulnerability. Do not share the suspected vulnerability or any data with others. Do not store or copy any unauthorized data. Doing any of these things will void eligibility for a bounty program reward.
- Email the details to our Security Incident Response Team at email@example.com.
- If the contents of the vulnerability are sensitive in nature, please use our PGP key found below to encrypt the information.
All reported vulnerabilities are checked for validity, ranked, and then reviewed by the Patron Technology InfoSec team.
Patron Technology has established a Vulnerability Ranking Matrix based on NIST's Common [Vulnerability Scoring System V3](https://nvd.nist.gov/vuln-metrics/cvss). The Vulnerability Ranking Matrix is defined below. Vulnerabilities are ranked using the guidelines below with assistance from the [NIST CVSS Calculator](https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator). The final ranking for a vulnerability is the sole discretion of Patron Technology InfoSec.
CVSS >= 9.0
Vulnerabilities that cause a privilege escalation on the platform from unprivileged to admin, allows remote code execution, financial theft, large scale access to PII, etc.. At the discretion of Patron Technology, vulnerabilities that demonstrate a critical, widespread risk to information security may be eligible to receive a reward greater than the standard bounty.
Example: Vulnerabilities that result in unrestricted Remote Code Execution such as Vertical Authentication bypass, SSRF, XXE, SQL Injection, User authentication bypass.
CVSS 7.0 - 8.9
Vulnerabilities that affect the security of the platform including the processes it supports.
Example: Lateral authentication bypass, Stored XSS, some CSRF depending on impact.
CVSS 5.0 - 6.9
Vulnerabilities that affect multiple users, and require little or no user interaction to trigger.
Example: Some reflective XSS, Some direct object reference, URL Redirect, some CSRF depending on impact.
CVSS < 5.0
Issues that affect singular users and require interaction or significant prerequisites (MITM) to trigger.
Example: Common flaws, Detailed debug information.
Non-exploitable weaknesses and “won’t fix” vulnerabilities.Best practices, mitigations, issues that are by design or acceptable business risk to the customer such as use of CAPTCHAS.
In Scope Domains
The following domains are included in this program.
In Scope Mobile Applications
The following categories of reports are considered out of scope for our program and Patron Technology will NOT provide any reward pay out:
- Any vulnerability with a CVSS 3 score lower than 4.0, unless it can be combined with other vulnerabilities to achieve a higher score.
- Brute force, DoS, phishing, text injection, or social engineering attacks. Wikis, Tracs, forums, etc are intended to allow users to edit them.
- Availability of XML-RPC file without PoC demonstrating a significant security impact. As noted above, this excludes DDoS and brute force attacks.
- Security vulnerabilities in WordPress plugins
- Self-XSS and issues exploitable only through Self-XSS
A Note about XSS
Please note: If you've identified an XSS issue (especially on our www site), please make sure it is actually exploitable beyond Burp Suite or whatever you're using. If you can't reproduce the XSS in a browser, we will likely consider it self-XSS, and an invalid submission.
- Mixed content warnings for passive assets like images and videos
- Clickjacking with minimal security implications
- Non critical issues that affect only outdated browsers.
- Cross-site Request Forgery (CSRF) with minimal security implications (Login/logout/unauthenticated)
A Note about CSRF
If you're reporting a CSRF issue and your POC includes the CSRF token, we will assume that you don't understand what CSRF issues are, nor how CSRF prevention works. Please don't report a CSRF vulnerability if your POC includes the CSRF token. (If you can get the CSRF token from a victim, show that.)
- Missing cookie flags on non-sensitive cookies.
- Reports of non-exploitable vulnerabilities and violation of “best practices” (e.g. Lack of HTTP security headers (CSP, X-XSS, etc.)
- Lack of secure/HTTP-only flags on non-session cookies
- Server error messages that do not contain internal, confidential or restricted data or avenues to obtain it
- DNS record configuration (SPF, DKIM, DMARC, CAA, DNSSEC, etc)
- Theoretical vulnerabilities where you can't demonstrate a significant security impact with a PoC.
- Some forms do not have rate limiting / brute-force protections. We will consider this out of scope for the program.
- Known issues that have been previously reported.
Changes to the Program
We may update or suspend this Program at any time without any prior notice. We encourage you to periodically review this page for the latest information on this Program. Any submitted reports will be processed using the Program terms in effect at the time our Security Incident Response Team reviews the report.