CVE-2017-18283
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 · uneditedPossible memory corruption when Read Val Blob Req is received with invalid parameters in Snapdragon Mobile in version QCA9379, SD 210/SD 212/SD 205, SD 625, 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 · high confidenceMemory corruption vulnerability in Qualcomm Snapdragon baseband/modem firmware occurs when processing a 'Read Val Blob Request' with invalid parameters, potentially allowing code execution or denial of service.
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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 Snapdragon chipset in your deviceCheck your device specifications, system information, or modem firmware details to determine if the chipset is one of: Qca9379, SD210, SD212, SD205, SD625, SD835, SD845, or SD850Affected if The device uses any of these chipsets, as all firmware versions for these models are affected
-
Determine the baseband/modem firmware versionAccess the device's modem information (typically via *#06# on mobile devices, or through engineering/ diagnostic modes, or by reading /proc/version or /sys/kernel/debug/rmnet debug files if available)Affected if Any firmware version is installed on an affected chipset, since all versions are vulnerable
-
Verify if the device exposes modem baseband interface to networkCheck whether the device's modem/baseband processor is directly accessible from untrusted network interfaces, or if diagnostic/engineering modes are enabled and reachableAffected if The baseband processor interface is exposed to untrusted networks or allows unauthenticated 'Read Val Blob Request' processing
If your device contains any of the listed Qualcomm Snapdragon chipsets (Qca9379, SD210, SD212, SD205, SD625, SD835, SD845, SD850) and the baseband interface is network-accessible, you are likely affected by this 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-supplied firmware/security patches from Qualcomm to the affected Snapdragon chipsets, then deploy via OTA updates to end devices. Until patched, restrict untrusted network exposure to affected devices.
- Consultation24.0 h
- Implementation60.0 h
- Testing40.0 h
- Review / QA16.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $39,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18283 — 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-18283 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