249 vulnerabilities rewarded
6 days average response time
$1,307.90 average payout (last 12 weeks)
Latest hall of famers
Tesla values the work done by security researchers in improving the security of our products and service offerings. We are committed to working with this community to verify, reproduce, and respond to legitimate reported vulnerabilities. We encourage the community to participate in our responsible reporting process.
For vehicle or product related services
While we use Bugcrowd as a platform for rewarding all issues, please report vehicle and product related issues directly to firstname.lastname@example.org, using our GPG key to encrypt reports containing sensitive information.
If issues reported to our bug bounty program affect a third-party library, external project, or another vendor, Tesla reserves the right to forward details of the issue to that party without further discussion with the researcher. We will do our best to coordinate and communicate with researchers through this process.
Responsible Disclosure Guidelines
We will investigate legitimate reports and make every effort to quickly correct any vulnerability. To encourage responsible reporting, we will not take legal action against you nor ask law enforcement to investigate you providing you comply with the following Responsible Disclosure Guidelines:
- Provide details of the vulnerability, including information needed to reproduce and validate the vulnerability and a Proof of Concept (POC).
- Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our services.
- Do not modify or access data that does not belong to you.
- Give Tesla a reasonable time to correct the issue before making any information public.
When registering for an account, please use your email@example.com email address.
Out of Scope
- Any SolarCity property, including *.solarcity.com
- Third-party websites hosted by non-Tesla entities, including:
- Tesla's public facing web applications.
- Vulnerabilities in other applications owned by Tesla.
- Vehicles or product related issues must be submitted by email in order to qualify for a reward, see above for instructions.
The following finding types are specifically excluded from the bounty:
- Internal IP address disclosure.
- Default files available via web (e.g. README.TXT, CHANGES.TXT, etc).
- Issues only useful in social engineering / phishing attacks (except in very rare cases)
- Lack of or weak password strength requirements.
- Self XSS (except for very special cases).
- Text injection (except for very special cases).
- Email spoofing (including SPF, DKIM, From: spoofing, and visually similar, and related issues).
- Descriptive error messages (e.g. stack traces, application or server errors).
- HTTP 404 codes/pages or other HTTP non-200 codes/pages.
- Fingerprinting/banner disclosure on common/public services.
- Full path disclosure / path disclosure (except for very special cases).
- Clickjacking and issues only exploitable through clickjacking.
- CSRF on forms that are available to anonymous users, for example contact forms.
- Disclosure of known public files or directories, (e.g. robots.txt).
- Login/Logout cross-site request forgery (CSRF).
- Presence of application or web browser ‘autocomplete’ or ‘save password’ functionality.
- Lack of Secure and HTTPOnly cookie flags (critical systems may still be in scope).
- Lack of security speedbump when leaving the site.
- Weak Captcha/Captcha bypass.
- Login or Forgot Password page brute force and account lockout not enforced.
- OPTIONS HTTP method enabled.
- HTTPS mixed content scripts.
- Username / email enumeration by brute forcing / error messages (e.g. login / signup / forgotten password).
- Exceptional cases may still be in scope (e.g. ability to enumerate email addresses via incrementing a numeric parameter).
- Missing HTTP security headers, including:
- Content-Security-Policy, X-Content-Security-Policy, X-WebKit-CSP
- TLS/SSL Issues, including:
- SSL Attacks such as BEAST, BREACH, Renegotiation attack.
- SSL Forward secrecy not enabled.
- SSL weak/insecure cipher suites.
- Denial of Service attacks.
- Out-of-date software.
- Open redirects.
We pay rewards ranging from $100 to $10,000. Rewards are administered according to the following guidelines:
- XSS: $200–$500
- CSRF: $100–$500
- SQL: $500–$10,000
- Command injection: Up to $10,000
- Authentication bypass: Up to $10,000
- Business logic issues: $100–$300
- Horizontal privilege escalation: $500
- Vertical privilege escalation: $500–$10,000
- Forceful browsing/Insecure direct object references: $100–$500
- Security misconfiguration: Up to $200
- Sensitive data exposure: Up to $300
- Vehicle or product related vulnerabilities: case-by-case (report directly, see above)
This program follows Bugcrowd’s standard disclosure terms.
This program does not offer financial or point-based rewards for Informational (P5) findings. Learn more about Bugcrowd’s VRT.
We support the open publication of security research. We do ask that you give us a heads-up before any publication so we can do a final sync-up and check.