Model S FirmwareOperating system · Tesla

CVE-2024-13943

HIGH · 7.8 CVSS v3.0 Published 2025-04-30
Fix available
A fix is available. Upgrade to 2024.8 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
Tesla Model S Iris Modem QCMAP_ConnectionManager Improper Input Validation Sandbox Escape Vulnerability. This vulnerability allows local attackers to escape the sandbox on affected affected Tesla Model S vehicles. An attacker must first obtain the ability to execute low-privileged code on the target system in order to exploit this vulnerability. The specific flaw exists within the QCMAP_ConnectionManager component. An attacker can abuse the service to assign LAN addresses to the WWAN. An attacker can leverage this vulnerability to access network services that were only intended to be exposed to the internal LAN. Was ZDI-CAN-23199.

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 · high confidence

This vulnerability in the Tesla Model S Iris Modem's QCMAP_ConnectionManager component allows a local attacker with low-privileged code execution to escape the sandbox by abusing improper input validation. The flaw enables assignment of LAN addresses to the WWAN interface, exposing internal-only network services to external interfaces.

MitigationTesla should release a firmware update that implements proper input validation in QCMAP_ConnectionManager to prevent LAN address assignment to WWAN, and enforce stricter sandboxing of the modem component.

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 S FirmwareOperating system
Affected:< 2024.8

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.0/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. Check Tesla Model S firmware version
    Access the vehicle's 'Software' menu via the touchscreen or check in the Tesla mobile app under 'Vehicle Details' to view the current firmware version
    Affected if The installed firmware version is earlier than 2024.8 (e.g., 2024.6, 2024.4, etc.)
  2. Verify QCMAP_ConnectionManager network configuration
    This requires diagnostic access to the Iris modem component. Using appropriate vehicle diagnostic tools or authorized service interfaces, inspect the QCMAP_ConnectionManager configuration for WWAN interface settings
    Affected if The WWAN interface has been assigned a LAN-side IP address (typically 192.168.x.x, 10.x.x.x, or 172.16-31.x.x ranges)
  3. Inspect exposed network services
    Using network scanning tools from an external interface (e.g., cellular connection), enumerate services listening on the WWAN or external-facing interfaces
    Affected if Services that should only be accessible internally (e.g., internal HTTP servers, diagnostic ports) are reachable from the external/WWAN interface

A Tesla Model S owner is affected if their vehicle firmware is older than version 2024.8 and the QCMAP_ConnectionManager misconfiguration allows internal network services to be exposed externally.

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.

From vendor data
Upgrade available Upgrade to 2024.8 or later
Fixed in 2024.8
Interim mitigation

Tesla should release a firmware update that implements proper input validation in QCMAP_ConnectionManager to prevent LAN address assignment to WWAN, and enforce stricter sandboxing of the modem component.

Fix this in Model S Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
42.0 hours of engineering $7,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 $11,712.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-2024-13943 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