CVE-2018-11830
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 · uneditedImproper input validation in QCPE create function may lead to integer overflow in Snapdragon Auto, Snapdragon Consumer Electronics Connectivity, Snapdragon Industrial IOT, Snapdragon Mobile in MDM9206, MDM9607, MDM9650, MDM9655, MSM8996AU, SD 410/12, SD 820A
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 confidenceThis is an integer overflow vulnerability in the QCPE (Quality of Service/Policy Control Element) create function caused by improper input validation. The vulnerability exists in Qualcomm Snapdragon chipset firmware and could allow an attacker to cause a buffer overflow or unexpected behavior by providing specially crafted input that triggers the integer overflow.
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 chipset modelCheck the device hardware specifications or read /proc/cpuinfo on Android devices to determine if the chipset is one of the following: Mdm9206, Mdm9607, Mdm9650, Mdm9655, Msm8996au, Snapdragon 410, Snapdragon 412, or Snapdragon 820aAffected if The device uses any of these Qualcomm chipset models
-
Check baseband firmware versionOn Android, go to Settings > About Phone > Baseband version or use AT command *#9999# or *#06# to access engineering mode. On other platforms, consult device documentation for how to view modem/baseband firmware informationAffected if The displayed baseband firmware version corresponds to any version of the affected chipsets (all versions are vulnerable)
-
Confirm QCPE component presenceThis is a low-level baseband component in the cellular firmware and is not user-accessible or configurable. The presence of the vulnerable chipset and firmware confirms the QCPE function exists in the systemAffected if The device runs the affected chipset firmware - the QCPE function is built into the baseband processor and cannot be disabled through user settings
A device is affected if it uses any of the listed Qualcomm chipsets (Mdm9206, Mdm9607, Mdm9650, Mdm9655, Msm8996au, Sd 410, Sd 412, Sd 820a) regardless of firmware version, as all versions contain the vulnerable QCPE create function
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 Qualcomm to device manufacturers; end users should accept OTA updates from their device vendors. The QCPE function is a low-level cellular/baseband component, so there are no user-configurable workarounds.
- Consultation8.0 h
- Testing16.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,552.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-11830 — 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-11830 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