dbcve.org
Ipq6018 FirmwareOperating system · Qualcomm

CVE-2019-10562

HIGH · 7.8 CVSS v3.1 Published 2020-09-08
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
u'Improper authentication and signature verification of debug polices in secure boot loader will allow unverified debug policies to be loaded into secure memory and leads to memory corruption' in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wired Infrastructure and Networking in IPQ6018, Kamorta, MSM8998, Nicobar, QCS404, QCS605, QCS610, Rennell, SA415M, SA6155P, SC7180, SDA660, SDA845, SDM630, SDM636, SDM660, SDM670, SDM710, SDM845, SDM850, SDX24, SDX55, SM6150, SM7150, SM8150, SM8250, SXR1130, SXR2130

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

The secure boot loader in affected Qualcomm Snapdragon chipsets fails to properly authenticate and verify signatures on debug policies before loading them into secure memory. This allows unverified or malicious debug policies to be loaded, leading to memory corruption and potential privilege escalation.

MitigationApply vendor-supplied firmware updates that patch the secure boot loader to enforce proper signature verification on debug policies before loading into secure memory.

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
Ipq6018 FirmwareOperating system
Affected:all versions
Kamorta FirmwareOperating system
Affected:all versions
Msm8998 FirmwareOperating system
Affected:all versions
Nicobar FirmwareOperating system
Affected:all versions
Qcs404 FirmwareOperating system
Affected:all versions
Qcs605 FirmwareOperating system
Affected:all versions
Qcs610 FirmwareOperating system
Affected:all versions
Rennell 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 the chipset model in your device
    Check your device documentation, hardware specifications, or use system commands (such as 'cat /proc/cpuinfo' or 'lspci' on Linux-based embedded systems) to determine the exact Qualcomm Snapdragon chipset present.
    Affected if The chipset matches any of the following: Ipq6018, Kamorta, Msm8998, Nicobar, Qcs404, Qcs605, Qcs610, or Rennell.
  2. Confirm the firmware version
    Retrieve the firmware version from your device's bootloader, UEFI settings, or system information interface (such as 'dmidecode' or vendor-specific diagnostic tools).
    Affected if The firmware version corresponds to any of the affected chipsets listed above, regardless of version number (all versions are affected).
  3. Verify secure boot status
    Check your device's secure boot configuration in UEFI/bootloader settings, or use vendor-provided tools to query the secure boot state. Look for whether secure boot is enabled and functioning.
    Affected if Secure boot is disabled, not properly configured, or fails to enforce signature verification on loaded policies.
  4. Check for debug policy configuration
    Inspect the bootloader or secure boot configuration for any debug policy settings or features. Look for debug policy loading mechanisms in the boot sequence.
    Affected if Debug policies can be loaded without signature verification, or debug policy loading is enabled without proper authentication checks.
  5. Review boot logs for policy loading anomalies
    Examine boot logs, bootloader debug output, or secure boot event logs for any warnings, failures, or unusual messages related to policy loading, signature verification, or memory initialization.
    Affected if Logs show failed signature checks, unverified policies being loaded, or memory corruption events during the boot process.

Your environment is affected if your device uses any of the listed Qualcomm Snapdragon chipset models (Ipq6018, Kamorta, Msm8998, Nicobar, Qcs404, Qcs605, Qcs610, or Rennell) and you rely on the secure boot loader to verify debug policy signatures before loading into secure memory.

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-supplied firmware updates that patch the secure boot loader to enforce proper signature verification on debug policies before loading into secure memory.

Fix this in Ipq6018 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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