CVE-2018-11824
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 · uneditedA stack-based buffer overflow can occur in a firmware routine in Snapdragon Mobile, Snapdragon Wear in version MDM9206, MDM9607, MDM9650, SD 210/SD 212/SD 205, SD 835, SD 845, SD 850, SDA660
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-based buffer overflow vulnerability exists in a firmware routine within Qualcomm Snapdragon mobile and wearable chipsets. The overflow occurs in the firmware layer, potentially allowing an attacker to overwrite stack memory and potentially execute arbitrary code. The affected components include MDM9206, MDM9607, MDM9650, SD 210/SD 212/SD 205, SD 835, SD 845, SD 850, and SDA660.
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 device chipset modelOn Android devices, go to Settings > About Phone and note the Model number and Baseband version. On feature phones or IoT devices, check product documentation or use AT commands (such as AT+CGMM) to query the modem model.Affected if The chipset model matches MDM9206, MDM9607, MDM9650, SD 210, SD 212, SD 205, SD 835, SD 845, SD 850, or SDA660
-
Verify firmware versionCheck the baseband or firmware version through Settings > About Phone > Baseband version, or use device diagnostic tools. Record the full firmware version string.Affected if The device is running any firmware version on an affected chipset (the advisory lists all versions as affected)
-
Confirm chipset is Qualcomm SnapdragonCross-reference the device model number with the chipset specifications from the manufacturer website or product documentation. Qualcomm Snapdragon chipsets are typically listed in technical specifications.Affected if The confirmed chipset is one of the listed affected Snapdragon models and the vulnerability is in the firmware layer rather than a user-accessible software service
If the device uses a Qualcomm Snapdragon chipset matching MDM9206, MDM9607, MDM9650, SD 210/212/205, SD 835, SD 845, SD 850, or SDA660, the device is affected since all firmware versions for these chipsets are vulnerable.
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 dataApply firmware updates provided by device manufacturers that incorporate Qualcomm's patched firmware for the affected Snapdragon chipsets. Until updates are available, reduce attack surface by avoiding untrusted network connections and applications.
- Consultation4.0 h
- Implementation2.0 h
- Testing8.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,640.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-11824 — 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-2018-11824 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