dbcve.org
Model S FirmwareOperating system · Tesla

CVE-2024-6031

HIGH · 7.8 CVSS v3.0 Published 2025-04-30
Fix available
A fix is available. Upgrade to 2024.2 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 oFono AT Command Heap-based Buffer Overflow Code Execution Vulnerability. This vulnerability allows local attackers to execute arbitrary code on affected Tesla Model S vehicles. An attacker must first obtain the ability to execute code on the target modem in order to exploit this vulnerability. The specific flaw exists within the parsing of responses from AT commands. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a heap-based buffer. An attacker can leverage this vulnerability to execute code in the context of the device. Was ZDI-CAN-23198.

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

A heap-based buffer overflow vulnerability exists in the oFono component of Tesla Model S vehicles when parsing AT command responses. The flaw results from insufficient length validation before copying user-supplied data to a heap-allocated buffer, allowing an attacker with prior modem code execution to achieve code execution in the device context.

MitigationTesla should implement proper bounds checking on AT command response data lengths before heap buffer allocation and copying. Users should apply any available vehicle firmware updates addressing this vulnerability.

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

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 vehicle firmware version
    Navigate to the vehicle's center screen Settings > Software and note the displayed firmware version, or use the vehicle's service mode to retrieve the firmware build number
    Affected if The installed firmware version is earlier than 2024.2 (any version below this threshold indicates the vulnerability may be present)
  2. Verify oFono component is active
    Check if the oFono modem management service is running on the vehicle's infotainment system. This can be confirmed through service mode diagnostics or by examining active system processes related to modem communication
    Affected if The oFono component is present and handles AT command processing on the vehicle's modem interface
  3. Confirm modem interface is accessible
    Verify that the cellular modem interface (typically accessed via /dev/ AT command interfaces) is available for communication. This may require service mode or diagnostic tools to inspect modem status
    Affected if The modem AT command interface is active and oFono is parsing responses from it
  4. Identify prior modem code execution indicators
    Review any logs or forensic artifacts that might indicate compromise of the modem subsystem. Look for unusual AT command patterns, unexpected modem resets, or signs of code execution at the modem level
    Affected if An attacker has already achieved code execution on the modem, which is a prerequisite for exploiting this vulnerability

A Tesla Model S vehicle is affected if its firmware version is earlier than 2024.2 and the attacker has already achieved prior code execution on the cellular modem subsystem to trigger the oFono heap overflow during AT command response parsing.

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 2024.2 or later
Fixed in 2024.2
Interim mitigation

Tesla should implement proper bounds checking on AT command response data lengths before heap buffer allocation and copying. Users should apply any available vehicle firmware updates addressing this vulnerability.

Recommended fix High confidence

Model S Firmware 2024.2

  1. Navigate to the Tesla vehicle's main touchscreen display
  2. Access the vehicle's 'Software' settings menu
  3. Check for available software updates using the 'Software Update' option
  4. Verify the update is version 2024.2 or later
  5. Download and install the firmware update following on-screen prompts
  6. Ensure the vehicle remains powered and connected during the update process
  7. After installation, verify the firmware version reflects 2024.2 or newer

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

Fix this in Model S Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-6031 — 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-2024-6031 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