This will happen some day, so invest 5 bucks per month to exploit Tesla at a certain point, so maybe you can be first in line for the Cybertruck :-)
I used to keep a hall of shame on my main site, because looking for "settings.php" or "global.asa" on a Zope site was just silly.
- https://www.tesla.com/.git/info/exclude
- https://www.tesla.com/.git/index
README.txt 403s too. https://www.tesla.com/README.txt
edit: just going to add files I've found here:
I accidentally ordered my model 3 with a free reservation, not the one I actually paid for.
Yes PHP is still relevant!
https://www.tesla.com/robots.txt
Disallow: /taxonomy/term/*
$ curl -si https://www.tesla.com/ | grep generator
x-generator: Drupal 9 (https://www.drupal.org)
$ curl -si https://www.tesla.com/authorize.php | grep generator
x-generator: Drupal 7 (http://drupal.org)
So they have at least two versions running at the same time. The /authorize.php [1] uri also yields a 500 (instead of a 403 like most of the other resources), which implies Apache is most likely passing the request off to PHP and the script has a fatal or unhandled error.The webroot appears to be a Drupal 7.x installation and Apache is serving that content directly (e.g. https://www.tesla.com/MAINTAINERS.txt same as [2]) and trying to run some of it (authorize.php), while happy-path requests are being reverse-proxied to a Drupal 9.x installation.
[1] https://github.com/drupal/drupal/blob/7.x/authorize.php
[2] https://github.com/drupal/drupal/blob/7.x/MAINTAINERS.txt
Usually these marketing sites are running a CMS (this one looks like Drupal) which is owned and operated by either an internal team who report to the CIO / IT department (vs the Product/Engineering group) or a totally external third-party marketing firm.
As long as the "real" product uses different subdomains, certificates, proper HSTS, cross-origin protection, and secure cookies (a tall order, yes, but something that would be an issue no matter what the marketing site is doing), security issues in the "marketing" site aren't as bad. Of course a marketing site takeover is still worrying, as it's a prime entry point for spearphishing and horizontal movement through social engineering, but these usually aren't the same engineers or security team at all.
Saved version:
TypeError: Cannot read property '0' of null
at forceFontAssetSource (/app/routes/middleware/moduleVersion.js:89:32)
at Layer.handle [as handle_request] (/app/node_modules/@tesla/design-system-tools/node_modules/express/lib/router/layer.js:95:5)
at trim_prefix (/app/node_modules/@tesla/design-system-tools/node_modules/express/lib/router/index.js:317:13)
at /app/node_modules/@tesla/design-system-tools/node_modules/express/lib/router/index.js:284:7
at Function.process_params (/app/node_modules/@tesla/design-system-tools/node_modules/express/lib/router/index.js:335:12)
at next (/app/node_modules/@tesla/design-system-tools/node_modules/express/lib/router/index.js:275:10)
at cors (/app/node_modules/cors/lib/index.js:188:7)
at /app/node_modules/cors/lib/index.js:224:17
at originCallback (/app/node_modules/cors/lib/index.js:214:15)
at /app/node_modules/cors/lib/index.js:219:13