dbcve.org
Aqt1000 FirmwareOperating system · Qualcomm

CVE-2020-11194

HIGH · 7.8 CVSS v3.1 Published 2021-02-22
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
Possible out of bound access in TA while processing a command from NS side due to improper length check of response buffer in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wired Infrastructure and Networking

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

A Trusted Application (TA) running in a TEE (Trusted Execution Environment) has an out-of-bounds memory access vulnerability due to improper length validation when processing commands from the non-secure (NS) world. This could allow an attacker in the non-secure domain to potentially access or corrupt memory outside the intended response buffer in the secure world.

MitigationApply vendor-supplied firmware/security updates for affected Snapdragon chipsets; contact device manufacturers for patch availability and deployment schedules.

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
Aqt1000 FirmwareOperating system
Affected:all versions
Ar8035 FirmwareOperating system
Affected:all versions
Pm3003a FirmwareOperating system
Affected:all versions
Pm4125 FirmwareOperating system
Affected:all versions
Pm4250 FirmwareOperating system
Affected:all versions
Pm456 FirmwareOperating system
Affected:all versions
Pm6125 FirmwareOperating system
Affected:all versions
Pm6150 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 device chipset model
    Check your device specifications or system information to determine if it uses a Qualcomm Snapdragon chipset that incorporates the affected firmware components (Aqt1000, Ar8035, Pm3003a, Pm4125, Pm4250, Pm456, Pm6125, or Pm6150). On Android, this is typically found in Settings > About Phone > Model/Chipset, or via terminal command: 'getprop ro.hardware' or 'cat /proc/cpuinfo'.
    Affected if The device uses a Qualcomm chipset that includes any of the listed firmware components (PMIC, audio, or network firmware)
  2. Check TEE/Trusted Application configuration
    Since this vulnerability resides in Trusted Applications running within the TEE, inspect whether TEE is enabled and which Trusted Applications are loaded. On Android devices, this may require root access and examination of /vendor/etc/ or /tee/ directories, or using tools like 'tee-supplicant' to query TEE status.
    Affected if The device has an active TEE with Trusted Applications that process commands from the non-secure (NS) world
  3. Verify firmware version of affected components
    For the specific PMIC (Power Management IC) or audio/network firmware components, check the installed firmware version. On Android, this may be visible in /sys/firmware/devicetree/, through 'dmesg' output, or via manufacturer-specific diagnostic tools. The affected components are: Aqt1000, Ar8035, Pm3003a, Pm4125, Pm4250, Pm456, Pm6125, and Pm6150 firmware.
    Affected if Any of these specific firmware components (PmXXXX or Aqt/Ar) are present in the system, as all versions are affected per the advisory

A device is affected if it incorporates any of the listed Qualcomm firmware components (Pm3003a, Pm4125, Pm4250, Pm456, Pm6125, Pm6150, Aqt1000, or Ar8035) and has an active TEE processing commands from the non-secure world.

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/security updates for affected Snapdragon chipsets; contact device manufacturers for patch availability and deployment schedules.

Fix this in Aqt1000 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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