CVE-2017-18274
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 · uneditedWhile iterating through the models contained in a fixed-size array in the actData structure, which also stores an incorrect number of models that is greater than the size of the array, a buffer overflow occurs in Snapdragon Automobile, Snapdragon Mobile, Snapdragon Wear in MDM9206, MDM9607, MDM9650, SD 210/SD 212/SD 205, SD 425, SD 430, SD 450, SD 617, SD 625, SD 650/52, SD 820, SD 820A, SD 835
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 confidenceA buffer overflow vulnerability exists in Qualcomm Snapdragon chipsets where the actData structure stores an incorrect model count that exceeds the size of a fixed-size array. When code iterates through models using this inflated count, it writes beyond the array boundaries, leading to memory corruption.
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 dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Qualcomm chipset modelCheck your device specifications or system information to determine the exact Qualcomm Snapdragon or MDM chipset model (e.g., Mdm9206, Sd 425, etc.)Affected if The chipset model matches one of: Mdm9206, Mdm9607, Mdm9650, Sd 210, Sd 212, Sd 205, Sd 425, or Sd 430
-
Verify firmware version on the chipsetAccess the device's baseband/firmware version information (typically found in Settings > About Phone > Baseband or through AT commands on modems)Affected if The device runs any firmware version on an affected chipset listed above - all versions are vulnerable
-
Confirm the actData functionality is in useThis is a firmware-level internal structure; users cannot directly inspect actData. The vulnerability exists in the baseband processor firmware handling model enumeration.Affected if The device uses the affected chipset firmware - the buffer overflow occurs during model count iteration in actData regardless of configuration
If your device contains any of the listed Qualcomm chipsets (Mdm9206, Mdm9607, Mdm9650, Sd 210, Sd 212, Sd 205, Sd 425, Sd 430) with any firmware version, you are affected by this buffer overflow vulnerability in the actData structure.
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.
From vendor dataThis firmware-level vulnerability requires a patch from Qualcomm that must be integrated and distributed by device manufacturers. Users should apply OEM/firmware updates as they become available.
- Consultation8.0 h
- Implementation16.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 $13,312.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18274 — 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-2017-18274 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