dbcve.org
Aqt1000Hardware / appliance · Qualcomm

CVE-2020-11180

HIGH · 7.8 CVSS v3.1 Published 2021-01-21
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
Out of bound access in computer vision control due to improper validation of command length before processing it in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile

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

Memory corruption vulnerability in Qualcomm Snapdragon chipset computer vision control component allows out-of-bounds read/write access due to improper validation of command length before processing. The flaw enables local privileged attackers to potentially execute arbitrary code or cause denial of service via specially crafted commands.

MitigationApply Qualcomm firmware updates (processor firmware patches) and device manufacturer updates as they become available. Until patch deployment, minimize attack surface by restricting access to untrusted applications and inputs.

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
Aqt1000Hardware / appliance
Affected:all versions
Pm3003aHardware / appliance
Affected:all versions
Pm6150Hardware / appliance
Affected:all versions
Pm7150aHardware / appliance
Affected:all versions
Pm7150lHardware / appliance
Affected:all versions
Pm7250Hardware / appliance
Affected:all versions
Pm7250bHardware / appliance
Affected:all versions
Pm8004Hardware / appliance
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 Qualcomm chipset model in the system
    Check system information via `lspci` (for PCIe connected chips), `lsusb` (for USB connected), or check device tree files in `/sys/firmware/devicetree/base/` for compatible string. On Android, check `Settings > About Phone > Hardware` or use `getprop` commands.
    Affected if The chipset model matches any of: Aqt1000, Pm3003a, Pm6150, Pm7150a, Pm7150l, Pm7250, Pm7250b, or Pm8004
  2. Check the power management IC (PMIC) firmware version
    Access PMIC firmware information through manufacturer-specific diagnostic tools, boot logs, or system management interfaces. On some devices, check `/sys/firmware/qcom-*.fw` or review early boot dmesg output for PMIC firmware version strings.
    Affected if The PMIC firmware version is present and the underlying PMIC hardware is one of the affected models (all versions are vulnerable)
  3. Determine if the computer vision control component is active
    Review system logs and active kernel modules for computer vision subsystem initialization. Check if any computer vision or CV-related services, drivers, or processes are running (look for terms like 'cv', 'computer_vision', 'vision' in process lists or module listings).
    Affected if The computer vision control component subsystem is loaded or enabled on the device
  4. Check for untrusted application access to CV subsystem
    Review application permission policies and SELinux/security policies for processes allowed to interface with the computer vision subsystem. Examine if any untrusted or third-party applications have elevated privileges to hardware components.
    Affected if Untrusted applications have permission to send commands to the CV control component or interact with the vulnerable PMIC subsystem

The environment is affected if the device uses any of the listed Qualcomm PMICs (Aqt1000, Pm3003a, Pm6150, Pm7150a, Pm7150l, Pm7250, Pm7250b, Pm8004) with the computer vision control component enabled and accessible.

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 Qualcomm firmware updates (processor firmware patches) and device manufacturer updates as they become available. Until patch deployment, minimize attack surface by restricting access to untrusted applications and inputs.

Fix this in Aqt1000 Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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