# CVE-2022-23126: Auth bypass in n/a

> Attackers can bypass authentication via Grafana to obtain Tesla API tokens, enabling remote vehicle control and door opening.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Jan 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-v336-j6w6-qhrr

## What is CVE-2022-23126?

CVE-2022-23126 is a critical authentication bypass vulnerability in n/a, published on 24 Jan 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### 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.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2022-23126?

It affects 1 product.


Products: Teslamate Teslamate.

## How do I fix CVE-2022-23126?

No fix has been published for CVE-2022-23126 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-23126 being exploited?

There is no known exploitation of CVE-2022-23126 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2023-31634](https://insights.sbomify.com/CVE-2023-31634/): Auth bypass in n/a (critical 9.8)
- [CVE-2023-29857](https://insights.sbomify.com/CVE-2023-29857/): Information disclosure in n/a (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-23126 and fix it if it is affected.

What it is: CVE-2022-23126 is a critical authentication bypass vulnerability in n/a, published on 24 Jan 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-23126 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-23126/ (Markdown: https://insights.sbomify.com/CVE-2022-23126/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-23126
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-23126
- OSV: https://osv.dev/vulnerability/CVE-2022-23126

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-23126/
Summaries are generated and may contain mistakes; the official description above is the record.