CVE-2019-13582
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 · uneditedAn issue was discovered in Marvell 88W8688 Wi-Fi firmware before version p52, as used on Tesla Model S/X vehicles manufactured before March 2018, via the Parrot Faurecia Automotive FC6050W module. A stack overflow could lead to denial of service or arbitrary code execution.
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 confidenceA stack buffer overflow vulnerability exists in Marvell 88W8688 Wi-Fi firmware versions prior to p52, as deployed in Tesla Model S/X vehicles through the Parrot Faurecia FC6050W module. The overflow can be exploited to cause denial of service or achieve arbitrary code execution on the affected Wi-Fi chip.
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< p52CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Wi-Fi hardware moduleInspect the vehicle's infotainment system or network components to determine if the Parrot Faurecia FC6050W module is present. This may require accessing the hardware BOM, service documentation, or diagnostic tools for the affected Tesla Model S/X vehicles.Affected if The Parrot Faurecia FC6050W module is present in the vehicle
-
Verify Marvell 88W8688 chip presenceConfirm that the Marvell 88W8688 Wi-Fi chip is integrated within the FC6050W module. This may be verifiable through hardware inspection, module firmware identification, or vehicle diagnostic interfaces.Affected if The Marvell 88W8688 Wi-Fi chip is present in the system
-
Retrieve the firmware versionUse appropriate diagnostic or firmware extraction methods to read the current firmware version installed on the Marvell 88W8688 chip. This may require specialized automotive diagnostic tools or direct firmware dumping from the module.Affected if A firmware version can be retrieved from the chip
-
Compare version against affected rangeCompare the retrieved firmware version against the affected range: versions prior to p52. Ensure the exact version string is identified (e.g., p51, p50, or earlier).Affected if The installed firmware version is less than p52 (for example, p51, p50, or any earlier version)
The environment is affected if the Parrot Faurecia FC6050W module with the Marvell 88W8688 chip is present and its firmware version is below p52.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpdate the Marvell 88W8688 Wi-Fi firmware to version p52 or later; Tesla vehicles require the manufacturer-provided security update for affected model years.
p52 (or later)
- Identify the Marvell 88W8688 Wi-Fi firmware version currently installed on the affected device or vehicle infotainment system
- Contact the device manufacturer (Tesla for vehicle applications, or Parrot Faurecia for the FC6050W module) to obtain the firmware update to version p52 or later
- Apply the firmware update following the manufacturer-provided instructions for the specific hardware platform
- Verify that the firmware has been successfully updated to version p52 or later
- Confirm the vulnerability is remediated through validation testing or manufacturer verification
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation4.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,856.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-13582 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-13582 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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