dbcve.org
Sd 210 FirmwareOperating system · Qualcomm

CVE-2017-8275

CRITICAL · 9.8 CVSS v3.0 Published 2018-04-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
In Android before security patch level 2018-04-05 on Qualcomm Snapdragon Mobile SD 210/SD 212/SD 205, SD 400, SD 430, SD 450, SD 617, SD 625, SD 650/52, SD 800, SD 808, SD 820, SD 835, an integer overflow vulnerability exists in a video library.

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 confidence

Integer overflow vulnerability in a video library affecting specific Qualcomm Snapdragon chipsets (SD 210/212/205, SD 400, SD 430, SD 450, SD 617, SD 625, SD 650/52, SD 800, SD 808, SD 820, SD 835) on Android devices before the 2018-04-05 security patch level. The vulnerability is exploitable remotely (likely via malicious video content) and can lead to code execution with CVSS 9.8 indicating critical impact.

MitigationApply Android security patch level 2018-04-05 or later; if devices cannot be updated, implement network-level filtering and restrict video processing to trusted content sources to reduce attack surface.

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 data
Sd 210 FirmwareOperating system
Affected:all versions
Sd 212 FirmwareOperating system
Affected:all versions
Sd 205 FirmwareOperating system
Affected:all versions
Sd 400 FirmwareOperating system
Affected:all versions
Sd 430 FirmwareOperating system
Affected:all versions
Sd 450 FirmwareOperating system
Affected:all versions
Sd 617 FirmwareOperating system
Affected:all versions
Sd 625 FirmwareOperating system
Affected:all versions

CVSS 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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Snapdragon chipset model
    Check the processor/chipset information via Settings > About Phone > Processor or by reading /proc/cpuinfo and look for the Snapdragon model number
    Affected if The chipset is one of SD 210, SD 212, SD 205, SD 400, SD 430, SD 450, SD 617, SD 625, SD 650, SD 652, SD 800, SD 808, SD 820, or SD 835
  2. Check the Android security patch level
    Navigate to Settings > About Phone > Security patch level, or run the command `getprop ro.build.version.security_patch` in a terminal or via ADB
    Affected if The security patch level is earlier than 2018-04-05 (for example, shows April 2018 or earlier, or any date in 2017)
  3. Confirm video library presence
    The vulnerable video library is part of the firmware on affected chipsets. No specific feature toggle to enable; the library is present by default on devices with the affected Snapdragon processors
    Affected if The device uses the vulnerable chipset and the video library component is included in the firmware (standard on all Android devices with these chipsets)

The device is affected if it contains one of the listed Snapdragon chipsets AND has a security patch level earlier than 2018-04-05.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Android security patch level 2018-04-05 or later; if devices cannot be updated, implement network-level filtering and restrict video processing to trusted content sources to reduce attack surface.

Recommended fix High confidence

Android Security Patch Level 2018-04-05 or later

  1. Check your device's current Android security patch level in Settings > About Phone > Security Patch Level
  2. If the security patch level is before April 5, 2018, check for system updates from your device manufacturer
  3. Apply the available Android security update that includes the 2018-04-05 patch level or later
  4. After updating, verify the security patch level reflects April 2018 or newer
  5. If no update is available from your device manufacturer, consider contacting the manufacturer or exploring alternative support options
Caveat Device must support the April 2018 security patch; older or unsupported devices may not receive this update

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Sd 210 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,560
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-8275 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-8275 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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