dbcve.org
Mdm9206 FirmwareOperating system · Qualcomm

CVE-2018-3594

CRITICAL · 9.8 CVSS v3.0 Published 2018-04-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
In Android before security patch level 2018-04-05 on Qualcomm Snapdragon Automobile, Snapdragon Mobile, and Snapdragon Wear MDM9206, MDM9607, MDM9650, SD 210/SD 212/SD 205, SD 425, SD 430, SD 450, SD 615/16/SD 415, SD 617, SD 625, SD 650/52, SD 808, SD 820, SD 820A, SD 835, SD 845, while parsing a private frame in an ID3 tag, a buffer over-read can occur when comparing frame data with predefined owner identifier strings.

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 buffer over-read vulnerability exists in Qualcomm Snapdragon chipsets when parsing private frames within ID3 tags in media files. The vulnerability occurs during string comparison operations with predefined owner identifiers, allowing an attacker to read beyond buffer boundaries by supplying a malicious audio file with crafted ID3 private frame data.

MitigationApply the Android security patch level 2018-04-05 or later, which contains the vendor fix for this vulnerability. Users should ensure their device manufacturers have released and installed the relevant security update.

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
Mdm9206 FirmwareOperating system
Affected:all versions
Mdm9607 FirmwareOperating system
Affected:all versions
Mdm9650 FirmwareOperating system
Affected:all versions
Sd 210 FirmwareOperating system
Affected:all versions
Sd 212 FirmwareOperating system
Affected:all versions
Sd 205 FirmwareOperating system
Affected:all versions
Sd 820a FirmwareOperating system
Affected:all versions
Sd 425 FirmwareOperating system
Affected:all versions

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/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 checks

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

  1. Identify your device chipset
    Check the device specifications or use system information to determine the Qualcomm Snapdragon model (Mdm9206, Mdm9607, Mdm9650, Sd 210, Sd 212, Sd 205, Sd 820a, or Sd 425)
    Affected if The chipset matches one of the affected models listed in the CVE
  2. Confirm firmware version
    Check the firmware version of the Snapdragon chipset through device settings or manufacturer documentation
    Affected if The firmware version is any version (all versions are affected per the CVE)
  3. Check Android security patch level
    On Android devices, go to Settings > About Phone > Software Information and look for the Security Patch Level date
    Affected if The Security Patch Level is earlier than 2018-04-05 or the field shows an older/unknown date indicating the fix has not been applied
  4. Identify ID3 parsing usage
    Determine if applications on the device process media files (audio) that may contain ID3 tags - this includes music players, media libraries, or any app that reads audio file metadata
    Affected if The device processes audio files with ID3 tags and the chipset/firmware is in the affected list

A user is affected if their device uses one of the listed Qualcomm Snapdragon chipsets and the Android security patch level is earlier than 2018-04-05, as this is when the vendor fix was released.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Android security patch level 2018-04-05 or later, which contains the vendor fix for this vulnerability. Users should ensure their device manufacturers have released and installed the relevant security update.

Recommended fix High confidence

Android security patch level 2018-04-05 or later (contact device manufacturer for specific firmware version)

  1. Identify the device manufacturer and model using the affected Qualcomm Snapdragon component (MDM9206, MDM9607, MDM9650, SD 210, SD 212, SD 205, SD 820a, or SD 425)
  2. Contact the device manufacturer to obtain the firmware update that includes the Android security patch level 2018-04-05 or later
  3. Apply the manufacturer-provided firmware update to remediate the out-of-bounds read vulnerability in ID3 tag parsing
Caveat Device manufacturer updates may have varying availability depending on device model and carrier support

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

Fix this in Mdm9206 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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