dbcve.org
Model 3 FirmwareOperating system · Tesla

CVE-2022-42430

HIGH · 7.8 CVSS v3.1 Published 2023-03-29
Fix available
A fix is available. Upgrade to 2022.28 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
This vulnerability allows local attackers to escalate privileges on affected Tesla vehicles. An attacker must first obtain the ability to execute privileged code on the target system in order to exploit this vulnerability. The specific flaw exists within the handling of the wowlan_config data structure. The issue results from the lack of validating the existence of an object prior to performing operations on the object. An attacker can leverage this vulnerability to escalate privileges and execute arbitrary code in the context of root. Was ZDI-CAN-17543.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A local privilege escalation vulnerability in Tesla vehicle software allows attackers with existing privileged code execution to further escalate to root. The flaw exists in the wowlan_config data structure handler, which fails to validate object existence before performing operations on it. This lack of validation enables arbitrary code execution in root context.

MitigationApply Tesla software updates addressing the wowlan_config validation issue. Since exploitation requires prior privileged access, restrict unauthorized access to vehicle systems and diagnostic interfaces.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Model 3 FirmwareOperating system
Affected:< 2022.28

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Tesla Model 3 firmware version
    Access the vehicle's diagnostic or infotainment system settings to retrieve the current firmware version. This is typically found in the 'Software' or 'Vehicle Info' section of the vehicle's central screen, or via Tesla's service mode if available.
    Affected if The installed firmware version is lower than 2022.28
  2. Verify wowlan_config module presence
    Check if the wowlan_config data structure handler is present in the vehicle's software. This may be identifiable through service mode diagnostics or by reviewing the vehicle's software components if accessible via diagnostic tools.
    Affected if The wowlan_config handler is present and accessible in the firmware
  3. Confirm diagnostic interface accessibility
    Evaluate whether diagnostic interfaces (such as Tesla's service mode, OBD-II port access, or remote diagnostic endpoints) are exposed or accessible without proper authorization.
    Affected if Diagnostic interfaces are accessible to unauthorized parties, providing a potential path for the required prior privileged code execution
  4. Check for existing privileged access indicators
    Review vehicle system logs, audit trails, or security event logs for any evidence of prior privileged code execution or unusual root-level activity within the vehicle software.
    Affected if Logs or system state indicate prior privileged access has been achieved, which is a prerequisite for exploiting this escalation vulnerability

A Tesla Model 3 is affected if it is running firmware version 2022.28 or lower AND has accessible diagnostic interfaces that could provide the initial privileged code execution required to trigger the wowlan_config root escalation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2022.28 or later
Fixed in 2022.28
Interim mitigation

Apply Tesla software updates addressing the wowlan_config validation issue. Since exploitation requires prior privileged access, restrict unauthorized access to vehicle systems and diagnostic interfaces.

Recommended fix Moderate confidence

Tesla Model 3 Firmware 2022.28 or later

  1. Confirm current Tesla Model 3 firmware version via vehicle settings or Tesla mobile app
  2. Schedule a software update through the Tesla mobile app or vehicle interface
  3. Ensure vehicle is connected to Wi-Fi or has adequate cellular connectivity for the over-the-air update
  4. Allow the firmware update to complete fully without interrupting power
  5. After update, verify firmware version has been updated to 2022.28 or later
Caveat Firmware updates for vehicles typically include bug fixes and security patches; minor UI or feature changes may occur but no known breaking changes for this specific update

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Model 3 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing16.0 h
  • Review / QA8.0 h
48.0 hours of engineering $8,320
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $13,312.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-42430 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-42430 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data