CVE-2018-11879
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 · uneditedWhen the buffer length passed is very large, bounds check could be bypassed leading to potential buffer overwrite in Snapdragon Mobile in version SD 845
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 bounds check bypass vulnerability exists in Snapdragon Mobile (SD 845) where passing a very large buffer length allows an attacker to circumvent boundary checks, potentially leading to buffer overflow/overwrite. This is a memory corruption issue in the baseband or system-on-chip firmware.
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 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 Snapdragon SD 845 chipsetOn Android devices, run 'getprop ro.product.board' or check /proc/cpuinfo for 'SDM845' identifier. On Linux, check /proc/cpuinfo or use 'lscpu' to identify the SoC.Affected if The device does not show SDM845 or SD 845 identifier - not affected. If SDM845 is present, proceed to next check.
-
Check baseband firmware versionOn Android, run 'getprop gsm.version.baseband' or check AT command interface (if available) with 'AT+CGMR' to retrieve baseband firmware version.Affected if Any baseband version on SD 845 is affected since the CVE states all versions are vulnerable.
-
Verify security patch levelOn Android, run 'getprop ro.build.version.security_patch' to check the last applied security patch date.Affected if If patch level is earlier than June 2018 (the CVE disclosure month), the device is likely vulnerable. All SD 845 devices without specific vendor firmware updates are affected.
-
Check for vendor-specific firmware updatesConsult device manufacturer documentation or check system update settings for any available baseband/firmware updates specifically addressing CVE-2018-11879.Affected if If no specific CVE-2018-11879 fix has been applied to the baseband firmware, the device remains affected.
A device is affected if it contains a Qualcomm Snapdragon SD 845 chipset with any baseband firmware version that has not been specifically patched to address this bounds check bypass vulnerability.
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 vendor-provided firmware/security patches from Qualcomm and device manufacturers. Given the CVSS 7.8 score, prioritize patching on affected mobile devices running Snapdragon SD 845.
- Consultation10.0 h
- Testing16.0 h
- Review / QA12.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,496.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-11879 — 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-11879 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