Teslamate: Improper Authentication
CVE-2022-23126 is a critical-severity improper authentication vulnerability in Teslamate, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version 1.25.1 as the first without the flaw, so updating Teslamate to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 2.21% chance of exploitation within 30 days, higher than 83% of scored CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Update Teslamate to 1.25.1 or a later version.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
Version data comes from NVD's product matching. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 9.8 | Critical | NVD |
| CVSS 2.0 | 7.5 | High | NVD |
Official description
TeslaMate before 1.25.1 (when using the default Docker configuration) allows attackers to open doors of Tesla vehicles, start Keyless Driving, and interfere with vehicle operation en route. This occurs because an attacker can leverage Grafana login access to obtain a token for Tesla API calls.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Authentication
When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.
How developers prevent this class of flaw
- Use an authentication framework or library such as the OWASP ESAPI Authentication feature.
Timeline
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
- github.com/adriankumpf/teslamate/commit/fff6915e7364f83b3030f980d5743299c4e5260dThird Party Advisory
- github.com/adriankumpf/teslamate/compare/v1.25.0...v1.25.1Third Party Advisory
- github.com/adriankumpf/teslamate/releases/tag/v1.25.1Release Notes, Third Party Advisory
Third-party and government advisories
- twitter.com/teslascope/status/1481252837174624258Issue Tracking, Third Party Advisory
Other references
Recent Improper Authentication vulnerabilities
- 9.8 Critical severity
- 8.8 High severity
- 5.3 Medium severity
Zabbix Frontend Improper Access Control Exploited
- 9.8 Critical severity
Dahua IP Camera Authentication Bypass Exploited
- 9.8 Critical severity
Dahua IP Camera Authentication Bypass Exploited
- 9.1 Critical severity
October CMS Improper Authentication Exploited
Spotted an error? Tell us.