Tesla

Description

Overview 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. We will coordinate and communicate with researchers through the bug bounty process. For vehicle or energy products While we use Bugcrowd as a platform for rewarding all issues, please report vehicle and product related issues directly to [email protected], using our GPG key to encrypt reports containing sensitive information. Third-party bugs 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 notification to the researcher. Eligibility Note, Tesla's bug bounty program is in part facilitated through a third party (BugCrowd) who performs additional services and eligibility checks on our behalf. For example, Tesla may not issue payments if one or more of the following is applicable: You are a resident of a country under U.S. sanctions or live in a country that prohibits this type of program, You are under the age of 14 at the time of reporting, or between the age of 14 and 18 without explicit prior permission from a parent or guardian. You are currently (or were in the last 6 months) an employee of Tesla, a Tesla subsidiary, or third-party contractor with access to Tesla’s internal systems and networks. How the program works Security researchers and Tesla customers are encouraged to submit reports regarding the security measures used to protect Tesla products and services. When conducting security research, you are required to follow Responsible Disclosure Guidelines & Tesla’s Rules of Engagement (referred to as “Terms”), which are provided below. If a vulnerability is found, please document your findings thoroughly before sending them to us. This may include screenshots or videos of your findings. Members of Tesla’s team may contact you to confirm that we have received your submission, ask questions about your findings, and discuss how to reproduce them. Tesla may direct you to stop your activities in the event that your research impacts Tesla owned assets, Tesla vendors, or other customers. If directed to stop, you must immediately comply with the request. Tesla’s security team will then work with impacted business units to validate the findings. If Tesla can validate your findings and we determine that it is eligible for a reward under this program’s Terms, a bounty reward will be issued. You are responsible for the payment of all applicable taxes. TERMS 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, so long as you comply with the Terms. Do not access or modify data that does not belong to you . If you are able to gain access to or modify data that belongs to Tesla, other customers, or Tesla vendors during the course of your research, you must take the following actions: Immediately stop your activities, Disclose your findings to Tesla as soon as possible (but no later than 24 hours after discovery). Your findings should include details of the vulnerability, including information needed to reproduce and validate the vulnerability and a Proof of Concept (POC), Wait for further instruction from the Tesla team. Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our services. Give Tesla a reasonable time to correct the issue before making any information public. In certain circumstances, Tesla may request that you not disclose your findings or to delay disclosure until we can ensure that the matter has been adequately addressed. You may not disclose confirmed, unresolved vulnerabilities without approval from Tesla. Rules of Engagement Research must be done using your own account or Tesla products that you own. You should not intentionally modify online accounts, data or products owned by other Tesla customers (without explicit permission). If during the course of your research, you find a vulnerability that would allow you to bypass an authentication control for another person’s account, you should report the vulnerability to Tesla immediately and take no further action. If you are able to access or modify personal data of other customers or other sensitive data that does not belong to you, immediately contact Tesla. Do not attempt to conduct post-exploitation work with this data. Where you are able to access data that does not belong to you, you will be asked to delete it. You must comply with this request, demonstrate the steps you took to ensure it was deleted, and confirm deletion to Tesla in order to be eligible for a reward. Do not attempt to use brute force or denial of service attacks on Tesla-owned systems without prior written approval. Hardware Research Registration Hardware Research Registration: If you are performing good-faith bug bounty related research on hardware that you own (vehicles or Powerwall, for example), you must first register the hardware with Tesla via [email protected]. This is necessary to prevent warranty-related issues. Registering also permits Tesla to voluntarily support researchers by providing updates or a “reflash” of the researcher-owned vehicle or Powerwall.

Targets

When registering for an account, please use your [email protected] email address. Please refrain from spamming forms (order forms, contact forms, etc) with high numbers of requests. Focus Area 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 findings are out of scope: Tesla account MFA issues are out of scope at the present time WAF bypass Open redirects / Lack of security speedbump when leaving the site Internal IP address disclosure Accessible Non-sensitive files and directories (e.g. README.TXT, CHANGES.TXT, robots.txt, .gitignore, WSDL, pprof, etc.) Social engineering / phishing attacks Self XSS Text injection Email spoofing (including SPF, DKIM, DMARC, From: spoofing, and visually similar, and related issues) Descriptive error messages (e.g. stack traces, application or server errors, path disclosure) Fingerprinting/banner disclosure on common/public services Clickjacking and issues only exploitable through clickjacking CSRF issues that don't impact the integrity of an account (e.g. log in or out, contact forms and other publicly accessible forms) Lack of Secure and HTTPOnly cookie flags (critical systems may still be in scope) Lack of rate limiting Login or Forgot Password page brute force, account lockout not enforced, or insufficient password strength requirements 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 TLS/SSL Issues, including BEAST BREACH, insecure renegotiation, bad cipher suite, expired certificates, etc. Denial of Service attacks Out-of-date software Use of a known-vulnerable component (exceptional cases, such as where you are able to provide proof of exploitation, may still be in scope) Physical attacks against Tesla's Facilities / Property Relay or RollJam attacks pertaining to the keyfob, NFC card, and/or phone-as-key Adversarial modification of the vehicle's environment to confuse Autopilot We still monitor for and appreciate hearing from researchers on new or novel findings in this area

Additional information

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.

Vehicle Targets (in scope)

Payout Guidelines The following section shows the range of payouts along with specific examples of impact. Within a category, the amount will depend on factors such as how much owner interaction is required, the capabilities of a compromised process (in the case of code execution), and the quality of the report. The below examples are not meant to be an exhaustive list of all valid findings within the program, but are meant to provide some clearer high-level guidelines and inspiration to researchers. If you have a security issue to report to us that does not fall into the below categories, please do not hesitate to reach out to us with your findings. We will continue to update the table with relevant categories and their associated payouts. If a vulnerability falls into multiple categories, the highest severity applies. Critical ($50,000 - $100,000) Remote zero-click to unconfined root on infotainment Any remote code execution on a CAN-connected ECU, e.g. Autopilot, VCSEC, Gateway Infotainment pivot to CAN-connected ECU, e.g. Autopilot, VCSEC, Gateway High ($20,000 - $50,000) Remote one-click to unconfined root on infotainment Unconfined root persistence on infotainment or Autopilot Remote zero-click on lower-privileged peripherals (WiFi/BT firmware, baseband) Local privilege escalation from unprivileged process Moderate ($10,000 - $20,000) Unprivileged remote code execution on infotainment Unconfined root on infotainment or Autopilot via ethernet Unconfined root on infotainment or Autopilot via USB Zero-click radio module remote code execution Low ($500 - $10,000) Unprivileged persistence on infotainment or Autopilot Local drive authentication bypass PIN-to-Drive bypass We do not award bounties for: Relay attacks Hardware-based glitching and side-channel attacks Confusing Autopilot by modifying the environment, such as adding lines to the road (CWE-XKCD-1958 attacks) Tesla-specific known issues (e.g., publicly reported or previously reported by another researcher) Chromium and/or Webkit bugs, unless chained with a full sandbox escape Persistence and/or secure boot bypasses on Tegra-based infotainment systems Attacks that require physical access on Tegra-based infotainment systems Payout Factors If a vulnerability affects multiple systems, e.g. shared code, bounty will be determined by the highest single amount with a bonus determined at Tesla's discretion The bounty amount may be reduced if the attack is unreliable, relies on unusual conditions being met, etc. A working proof-of-concept will help ensure you receive the maximum applicable payout for your report Internal duplicates that are not yet fixed will still be rewarded at a reduced amount Vulnerabilities affecting Tegra-based infotainment systems are rewarded at Tesla's discretion, along with a reduced payout Superchargers and related infrastructure are out of scope We may at our discretion award payouts for CVEs in third-party code that affect us, provided it's an unknown risk and the report demonstrates impact. Root access program To promote further security research, Tesla offers security researchers the opportunity to retain root access on their infotainment system even after their reported vulnerability has been patched. In order to qualify, a researcher must send in a valid report describing a novel way to gain root access on a Tesla infotainment system. Upon confirmation, Tesla will instruct the researcher on how to use their existing root access to enable the researcher SSH feature, along with an SSH certificate for the researcher's public key (tailored to their specific hardware ID). The certificate restricts SSH access to the local diagnostic ethernet link. Tesla may renew the certificate as long as the researcher continues reporting vulnerabilities.