Committed to Coordination

If you have information related to security vulnerabilities of General Motors products or services, we want to hear from you. Please submit a report in accordance with the guidelines below.

We value the positive impact of your work and thank you in advance for your contribution.

Guidelines

GM agrees to not pursue civil claims against researchers related to the disclosures submitted through this website who:

• do not cause harm to GM, our customers, or others;

• provide a detailed summary of the vulnerability, including the target, steps, tools, and artifacts used during discovery (the detailed summary will allow us to reproduce the vulnerability);

• do not compromise the privacy or safety of our customers and the operation of our services. Specifically;

  • contact us immediately if you inadvertently encounter user data;

  • do not view, alter, save, store, transfer, or otherwise access the data, and immediately purge any local information upon reporting the vulnerability to GM;

  • act in good faith to avoid privacy violations, destruction of data, and interruption or degradation of our services (including denial of service);

• comply with all applicable laws;

• do not violate any other law (other than those that would result only in claims by GM), or disrupt or compromise any data or vehicle that is not their own;

• publicly disclose vulnerability details only after GM confirms completed remediation of the vulnerability and not publicly disclose vulnerability details if there is no completion date or completion cannot be ascertained;

• confirm that they are not currently located in or otherwise ordinarily resident in Cuba, Iran, North Korea, Sudan, Syria or Crimea; and

• confirm that they are not on the U.S. Department of the Treasury’s Specially Designated Nationals List.

Out of Scope

1. Reports from automated tools or scans

2. Issues without clearly identified security impact (such as clickjacking on a static website), missing security headers, or descriptive error messages

3. Missing best practices, information disclosures, use of a known-vulnerable libraries or descriptive / verbose / unique error pages (without substantive information indicating exploitability)

4. Speculative reports about theoretical damage without concrete evidence or some substantive information indicating exploitability

5. Forms missing CSRF tokens without evidence of the actual CSRF vulnerability

6. Self-exploitation (e.g., cookie reuse)

7. Reports of insecure SSL / TLS ciphers (unless you have a working proof of concept, and not just a report from a scanner such as SSL Labs)

8. Our policies on presence/absence of SPF / DMARC records

9. Password complexity requirements, account/e-mail enumeration, or any report that discusses how you can learn whether a given username or email address has a GM-related account

10. Missing security-related HTTP headers which do not lead directly to a vulnerability

11. Self Cross-site Scripting vulnerabilities without evidence on how the vulnerability can be used to attack another user

12. POST-based Reflected Cross-site Scripting (XSS) vulnerabilities (Unless supporting documentation can be provided, illustrating how the vulnerability can be leveraged to exploit another entity directly from a GM trusted domain.)

13. Social engineering of GM employees or contractors

14. Any physical attempt against GM property or data centers

15. Presence of autocomplete attribute on web forms

16. Missing secure cookie flags on non-sensitive cookies

17. Denial of Service Attacks

18. Banner identification issues (e.g., identifying what web server version is used)

19. Open ports which do not lead directly to a vulnerability

20. Open redirect vulnerabilities

21. Publicly accessible login panels

22. Clickjacking

23. Content spoofing / text injection

24. Non-GM hosted dealership websites

Safe Harbor

GM agrees not to pursue civil action against researchers who comply with General Motors’ and HackerOne’s policies regarding this vulnerability disclosure program. We consider activities conducted consistent with the GM Policy Terms to constitute “authorized” conduct under the Computer Fraud and Abuse Act. Also, if you comply with the GM Policy Terms, we will not bring a DMCA claim against you for circumventing the technological measures we have used to protect the applications in scope.

If legal action is initiated by a third party against you and you have complied with the GM Policy Terms, we will, if asked, state that your actions were conducted in compliance with this policy.

By clicking Submit Report, you consent to Your Information being transferred to and stored in the United States and acknowledge that you have read and accepted the Terms, Privacy Policy and Disclosure Guidelines presented to you when you created your account.