CVE-2017-18310
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 · uneditedClientEnv exposes services 0-32 to HLOS in Snapdragon Automobile, Snapdragon Mobile, Snapdragon Wear in version MSM8909W, MSM8996AU, SD 210/SD 212/SD 205, SD 410/12, SD 425, SD 427, SD 430, SD 435, SD 450, SD 615/16/SD 415, SD 617, SD 625, SD 650/52, SD 810, SD 820, SD 820A, SD 835, SD 845, SDA660, SDM429, SDM439, SDM630, SDM632, SDM636, SDM660, Snapdragon_High_Med_2016
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 confidenceClientEnv component in Qualcomm Snapdragon chipsets exposes internal services 0-32 to the High Level Operating System (HLOS), potentially allowing unauthorized access to privileged operations or sensitive functions.
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 Qualcomm Snapdragon chipset modelCheck the device's system information, kernel logs, or hardware specifications to determine the exact Snapdragon chipset model (e.g., Msm8909w, Msm8996au, Sd 210, Sd 212, Sd 205, Sd 410, Sd 412, Sd 425)Affected if The chipset model matches any of the following: Msm8909w, Msm8996au, Sd 210, Sd 212, Sd 205, Sd 410, Sd 412, or Sd 425
-
Verify ClientEnv component is presentExamine the firmware image or system logs for the presence of the ClientEnv component (sometimes listed as clientenv, ClientEnv, or similar variants in firmware partitions or service listings)Affected if The ClientEnv component is found exposed to the HLOS in the firmware
-
Check if internal services 0-32 are accessible to HLOSReview system logs, service configurations, or kernel interfaces to determine whether internal services numbered 0 through 32 are exposed to the High Level Operating System (HLOS)Affected if Services 0-32 are exposed to and accessible by the HLOS
-
Confirm firmware is from the affected product lineCheck the baseband firmware version or modem firmware version reported by the device, and verify it corresponds to the listed affected productsAffected if The firmware corresponds to any of the affected chipset models listed, since all versions are impacted
A device is affected if it contains any of the listed Qualcomm Snapdragon chipset models (Msm8909w, Msm8996au, Sd 210, Sd 212, Sd 205, Sd 410, Sd 412, or Sd 425) and runs firmware where the ClientEnv component exposes internal services 0-32 to the HLOS.
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 firmware updates from device manufacturers; coordinate with Qualcomm for chipset-level patches.
- Consultation3.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18310 — 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-18310 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