dbcve.org
Sda845 FirmwareOperating system · Qualcomm

CVE-2019-10575

HIGH · 7.8 CVSS v3.1 Published 2020-04-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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
Wlan binary which is not signed with OEMs RoT is working on secure device without authentication failure in Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile in SDA845, SDM845, SDM850

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

A vulnerability in the WLAN subsystem of Snapdragon SDA845, SDM845, and SDM850 allows unsigned binaries to execute on devices with secure boot enabled, bypassing the OEM Root of Trust (RoT) signature verification. This indicates a failure in the secure boot chain validation for WLAN firmware, potentially allowing arbitrary code execution in a trusted execution environment.

MitigationApply vendor-provided firmware updates that enforce proper signature validation for WLAN binaries and ensure secure boot properly rejects unsigned code. Verify all device boot chains properly validate firmware signatures before execution.

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
Sda845 FirmwareOperating system
Affected:all versions
Sdm845 FirmwareOperating system
Affected:all versions
Sdm850 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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/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 checks

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

  1. Identify chipset model
    Check the device or system information to determine if the chipset is Qualcomm SDA845, SDM845, or SDM850. On Android, this can be found in /proc/cpuinfo or via 'getprop' commands. On Linux, check /proc/cpuinfo or dmesg for chip identification.
    Affected if The device uses SDA845, SDM845, or SDM850 chipset
  2. Verify secure boot status
    Check if secure boot is enabled on the device. On Android devices, this is typically found in the bootloader settings or via 'getprop ro.secureboot.locked' or checking the verified boot state in /sys/kernel/boot_params/data. OEM-specific tools or bootloader diagnostics may also show this status.
    Affected if Secure boot is enabled but the device uses an affected chipset (the bypass specifically affects devices with secure boot ON)
  3. Check WLAN firmware version
    Retrieve the WLAN firmware version from the device. On Android, this may be available via 'wpa_cli status', 'dmesg | grep wlan', or checking /sys/class/net/wlan0/device/firmware_version. On Linux systems, check 'iw list' or the wlan driver modules.
    Affected if The WLAN firmware is present on an affected chipset (SDA845/SDM845/SDM850)
  4. Verify secure boot chain validation for WLAN
    Inspect boot logs or audit logs for any failures or bypasses in signature validation for WLAN firmware. Check if the device's boot chain properly validates WLAN firmware binaries before execution. OEM diagnostics or secure boot audit logs may contain this information.
    Affected if Secure boot chain validation is missing or failing for WLAN firmware, or unsigned binaries can be loaded despite secure boot being enabled

A user is affected if their device uses a Qualcomm SDA845, SDM845, or SDM845 chipset, has secure boot enabled, and the WLAN subsystem allows unsigned binaries to execute, bypassing the OEM Root of Trust signature verification.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-provided firmware updates that enforce proper signature validation for WLAN binaries and ensure secure boot properly rejects unsigned code. Verify all device boot chains properly validate firmware signatures before execution.

Fix this in Sda845 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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