dbcve.org
Ipq8074 FirmwareOperating system · Qualcomm

CVE-2017-18330

HIGH · 7.8 CVSS v3.0 Published 2019-01-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Buffer overflow in AES-CCM and AES-GCM encryption via initialization vector in snapdragon automobile, snapdragon mobile and snapdragon wear in versions IPQ8074, MDM9206, MDM9607, MDM9635M, MDM9640, MDM9650, MDM9655, MSM8909W, MSM8996AU, SD 210/SD 212/SD 205, SD 410/12, SD 425, SD 427, SD 430, SD 435, SD 439 / SD 429, SD 450, SD 615/16/SD 415, SD 625, SD 632, SD 636, SD 650/52, SD 810, SD 820, SD 820A, SD 835, SDA660, SDM439, SDM630, SDM660, SDX24, Snapdragon_High_Med_2016.

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 AES-CCM and AES-GCM encryption implementations within Qualcomm Snapdragon processors (automobile, mobile, and wear variants) due to improper initialization vector (IV) handling. This could allow local or adjacent attackers to potentially execute arbitrary code or cause denial of service.

MitigationApply vendor security patches from Qualcomm and device manufacturers; update affected devices to patched firmware versions. No workarounds available for cryptographic implementation flaws.

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
Ipq8074 FirmwareOperating system
Affected:all versions
Mdm9206 FirmwareOperating system
Affected:all versions
Mdm9607 FirmwareOperating system
Affected:all versions
Mdm9635m FirmwareOperating system
Affected:all versions
Mdm9640 FirmwareOperating system
Affected:all versions
Mdm9650 FirmwareOperating system
Affected:all versions
Mdm9655 FirmwareOperating system
Affected:all versions
Msm8909w 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
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. Identify the Qualcomm chipset model
    Check system hardware information or device specifications to determine if the processor is one of: Ipq8074, Mdm9206, Mdm9607, Mdm9635m, Mdm9640, Mdm9650, Mdm9655, or Msm8909w. This can be done via /proc/cpuinfo, device documentation, or manufacturer specifications.
    Affected if The device uses any of the listed Qualcomm chipset models (all versions are affected)
  2. Determine firmware version
    Retrieve the current firmware version from the device system settings, boot logs, or via vendor-specific diagnostic tools. Compare against available patch information from the device manufacturer.
    Affected if Firmware has not been updated to a patched version released after the CVE disclosure date
  3. Check if AES-CCM encryption is in use
    Inspect application configurations, network traffic analysis, or system logs to determine whether AES-CCM mode encryption is being used for any cryptographic operations on the device.
    Affected if AES-CCM encryption is actively used on the affected hardware
  4. Check if AES-GCM encryption is in use
    Inspect application configurations, network traffic analysis, or system logs to determine whether AES-GCM mode encryption is being used for any cryptographic operations on the device.
    Affected if AES-GCM encryption is actively used on the affected hardware

The environment is affected if the device uses any of the listed Qualcomm chipsets (Ipq8074, Mdm9206, Mdm9607, Mdm9635m, Mdm9640, Mdm9650, Mdm9655, Msm8909w) with unpatched firmware and utilizes AES-CCM or AES-GCM encryption.

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

Apply vendor security patches from Qualcomm and device manufacturers; update affected devices to patched firmware versions. No workarounds available for cryptographic implementation flaws.

Fix this in Ipq8074 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Testing4.0 h
  • Review / QA4.0 h
16.0 hours of engineering $2,920
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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