dbcve.org
Ipq4019 FirmwareOperating system · Qualcomm

CVE-2015-9152

CRITICAL · 9.8 CVSS v3.0 Published 2018-04-18
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 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Automobile and Snapdragon Mobile IPQ4019, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 425, SD 427, SD 430, SD 435, SD 450, SD 615/16/SD 415, SD 625, SD 800, SD 810, SD 820, SD 820A, SD 835, and Snapdragon_High_Med_2016, modem owned regions are accessible from secure side.

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 confidence

This vulnerability in Qualcomm Snapdragon processors allows modem-owned memory regions to be accessible from the secure side, potentially enabling unauthorized access to protected memory areas. This represents a privilege separation failure where the boundary between the modem subsystem and the trusted execution environment is insufficiently enforced.

MitigationApply the Android security patch level from April 2018 or later, which contains the fix for this vulnerability. Users should verify their device has received the 2018-04-05 security update or later.

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
Ipq4019 FirmwareOperating system
Affected:all versions
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 410 FirmwareOperating system
Affected:all versions
Sd 412 FirmwareOperating system
Affected:all versions
Sd 425 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 Qualcomm Snapdragon chipset model
    Check the device specifications or use system information (e.g., 'cat /proc/cpuinfo' on Linux-based systems, or check 'Settings > About Phone' on Android) to determine the exact Snapdragon model number
    Affected if The chipset matches one of the affected models: Ipq4019, SD210, SD212, SD205, SD400, SD410, SD412, or SD425
  2. Check the Android security patch level
    On Android devices, go to 'Settings > Security > Security patch level' or run 'getprop ro.build.version.security_patch' via ADB
    Affected if The security patch level is earlier than 2018-04-05, or the field is empty/unavailable indicating the device has not received the April 2018 security update
  3. Verify the modem or baseband firmware version
    On Android, check 'Settings > About Phone > Baseband version' or use 'getprop gsm.version.baseband' via ADB. On router/access point devices, check the firmware information in the admin interface or via CLI
    Affected if The baseband/modem firmware is from an older release and the device has not applied the April 2018 patch

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 the Android security patch level from April 2018 or later, which contains the fix for this vulnerability. Users should verify their device has received the 2018-04-05 security update or later.

Recommended fix High confidence

Android Security Patch Level 2018-04-05 or later

  1. Check current Android Security Patch Level in Settings > About Phone > Android security patch level
  2. If the patch level is earlier than 2018-04-05, apply the latest available Android security update from your device manufacturer
  3. Contact your device manufacturer if the April 2018 security patch is not available for your device
  4. For embedded/IoT devices using these Snapdragon chipsets, contact the device vendor for firmware updates that include the April 2018 Qualcomm security fixes

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

Fix this in Ipq4019 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA3.0 h
17.0 hours of engineering $3,100
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-9152 — 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-2015-9152 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