CVE-2018-11867
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 · uneditedLack of buffer length check before copying in WLAN function while processing FIPS event, can lead to a buffer overflow 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 confidenceBuffer overflow vulnerability in WLAN function of Snapdragon SD 845 occurring during FIPS event processing due to missing bounds check before memory copy operation. The lack of buffer length validation allows an attacker to overflow the destination buffer when processing specially crafted FIPS events.
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 chipset modelCheck if the device or access point uses the Qualcomm Snapdragon SD 845 chipset. This information is typically available via device specifications, FCC filings, or by accessing the device's system information/boot logs.Affected if Device uses Snapdragon SD 845 chipset
-
Verify WLAN function is activeConfirm that the WLAN (Wi-Fi) functionality is enabled and operational on the affected device. This can be checked via the device's network settings, admin interface, or system logs showing wireless interface status.Affected if WLAN is enabled and active on SD 845 device
-
Confirm FIPS mode is in useCheck whether FIPS (Federal Information Processing Standards) mode is enabled on the wireless subsystem. This is typically configurable in enterprise or government-grade wireless设备的安全设置中，可能在WLAN配置界面或固件设置中显示为FIPS模式或加密合规选项。Affected if FIPS mode or FIPS-compliant encryption is enabled on the WLAN interface
Device is affected if it is a Snapdragon SD 845-based device with WLAN enabled and FIPS mode activated, as the buffer overflow occurs during FIPS event processing in the WLAN firmware.
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 Qualcomm firmware/security patch for Snapdragon SD 845; contact device OEM for platform-specific updates. If no patch available, consider network segmentation to limit exposure of affected wireless components.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-11867 — 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-11867 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