Fiat Chrysler Automobiles values engaging third party researchers to improve our products making them safer and more reliable. We have committed to formal recognition and compensation for discovery of reproducible and legitimate vulnerabilities, provided they are disclosed responsibly. Our goal with the Bug Bounty project is to foster a collaborative relationship with researchers to participate in responsible disclosure of vulnerabilities in FCA’s vehicles and connected services.
Responsible Disclosure Guidelines:
We will investigate legitimate reports and make every effort to correct any valid vulnerability as quickly as possible. In the spirit of encouraging responsible disclosure and reporting, we will not take legal action against nor ask law enforcement to investigate researchers participating in the program provided their compliance with the following Responsible Disclosure Guidelines:
- Provide full details of the vulnerability, including information needed to reproduce and validate the issue by producing Proof of Concept (code, technical demos of vulnerability, or necessary steps needed to demonstrate your finding)
- Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our services
- Do not modify, access, or retain data that does not belong to you
|Technical severity||Reward range|
|p1 Critical||$1,500 - $7,500|
|p2 Severe||$800 - $1,500|
|p3 Moderate||$450 - $800|
|p4 Low||$150 - $400|
Out of scope
This program is focused on the security of FCA’s connected vehicles, including the systems within them, and the external services and applications that interact with them.
Only the above domains and applications are in scope for the program. If the domain is not explicitly listed here, it is not considered in scope for the program and should NOT be tested.
Before starting research on an out-of-scope asset, please contact firstname.lastname@example.org. From there, we will work with FCA to confirm there is interest in the research, and to determine if testing can be conducted without causing a spike in errors or disruption of service. Note that out-of-scope findings may not be eligible for a monetary reward, which is at the discretion of FCA.
Before doing any testing that requires a Uconnect account, please create a test account that ends in @bugcrowdninja.com so that we know your activities are part of the Bug Bounty Program.
You can register for a new Uconnect account at: https://www.mopar.com/en-us/sign-in.html
This program uses a modified version of the standard priority guidelines presented in Bugcrowd's Vulnerability Rating Taxonomy.
The following finding types are specifically excluded from the bounty:
- We appreciate the high volume of submissions for XSS. We are temporarily removing this vulnerably from scope as we work to fix those issues
- Denial of Service attacks against any piece of FCA Infrastructure.
- Cross Site Request Forgery on non-authenticated pages
- Certificate strength issues
- Error messages (Descriptive or otherwise)
- HTTP Error pages
- Public service disclosure, such as banner pages
- Missing or misconfigured DMARC related findings
- Service Disruptions
- Public files or directories, (e.g. robots.txt)
- Clickjacking and issues only exploitable through clickjacking
- Web browser functionality controlled by the client, such as saved passwords and auto completion
- Login or Forgot Password page brute force and account lockout not enforced
- Vulnerabilities identified with automated tools (including web scanners) that do not include POC code or a demonstrated exploit
- Physical, social engineering, and phishing attempts
When conducting vulnerability research according to this policy, we consider this research to be:
Authorized in accordance with the Computer Fraud and Abuse Act (CFAA) (and/or similar state laws), and we will not initiate or support legal action against you for accidental, good faith violations of this policy;
Exempt from the Digital Millennium Copyright Act (DMCA), and we will not bring a claim against you for circumvention of technology controls;
Exempt from restrictions in our Terms & Conditions that would interfere with conducting security research, and we waive those restrictions on a limited basis for work done under this policy; and
Lawful, helpful to the overall security of the Internet, and conducted in good faith.
You are expected, as always, to comply with all applicable laws.
If at any time you have concerns or are uncertain whether your security research is consistent with this policy, please submit a report through one of our Official Channels before going any further.