dbcve.org
Mdm9650 FirmwareOperating system · Qualcomm

CVE-2018-3589

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 Mobile MDM9650, MDM9655, SD 835, SD 845, SD 850, the vswr capture size is larger than the maximum size of a diag logPacket, which can lead to a buffer overflow when the sample buffer is copied to the logPacket buffer.

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

Buffer overflow vulnerability in the diag logging component of Qualcomm Snapdragon processors (MDM9650, MDM9655, SD 835, SD 845, SD 850) where the vswr (Voltage Standing Wave Ratio) capture size exceeds the maximum allocated size for the diag logPacket buffer, causing overflow during sample buffer to logPacket buffer copy operations.

MitigationApply Android security patch level 2018-04-05 or later which contains the vendor fix for this buffer overflow in the Qualcomm diag component; this requires updating the device firmware/baseband processor.

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
Mdm9650 FirmwareOperating system
Affected:all versions
Mdm9655 FirmwareOperating system
Affected:all versions
Sd 835 FirmwareOperating system
Affected:all versions
Sd 845 FirmwareOperating system
Affected:all versions
Sd 850 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 the Qualcomm processor model
    Check /proc/cpuinfo or run 'getprop ro.hardware' or 'getprop ro.board.platform' to determine the chipset. For baseband info, check 'getprop gsm.version.baseband' or query AT*VERSION via serial/debug interface.
    Affected if The processor is one of: MDM9650, MDM9655, SD 835, SD 845, or SD 850
  2. Verify the diag logging component is active
    Check if diag logging interface is enabled. On Android, examine /dev/diag or check for 'diag' in /proc/devices. Verify if the device has diag daemon running via 'ps | grep diag' or check related services.
    Affected if The diag logging component is enabled and accessible on the device
  3. Confirm firmware/baseband version
    Retrieve baseband processor version via 'getprop gsm.version.baseband', AT command interface, or /proc/version. Compare against known affected firmware builds.
    Affected if Firmware is present on any of the affected chipset models (all versions of MDM9650, MDM9655, SD 835, SD 845, SD 850 are vulnerable)
  4. Check Android security patch level
    Run 'getprop ro.build.version.security_patch' to see the installed patch level.
    Affected if The security patch level is earlier than 2018-04-05, indicating the fix is not applied

The device is affected if it uses any of the listed Qualcomm processors (MDM9650, MDM9655, SD 835, SD 845, SD 850) and the Android security patch level is before 2018-04-05, or if the firmware has not been updated to include the vendor fix.

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 Android security patch level 2018-04-05 or later which contains the vendor fix for this buffer overflow in the Qualcomm diag component; this requires updating the device firmware/baseband processor.

Recommended fix Moderate confidence

Android devices with security patch level 2018-04-05 or later (contact device manufacturer for specific model-specific update availability)

  1. Identify the device model running the affected Qualcomm Snapdragon firmware (MDM9650, MDM9655, SD 835, SD 845, or SD 850)
  2. Check if your device manufacturer has released an Android security update with patch level 2018-04-05 or later
  3. If available, apply the Android security update through the device's system settings under Settings > Security > Security patch level
  4. Verify the installed patch level reflects 2018-04-05 or later after the update
Caveat Updating to the patched firmware may require accepting the full Android system update from your device manufacturer; some older devices may not receive this security patch

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

Fix this in Mdm9650 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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