dbcve.org
Apq8009 FirmwareOperating system · Qualcomm

CVE-2020-3643

MEDIUM · 5.5 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 →
57/100
Remediation priority · Elevated
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'Information disclosure issue can occur due to partial secure display-touch session tear-down' in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking in APQ8009, APQ8017, APQ8053, APQ8076, APQ8096AU, APQ8098, IPQ6018, Kamorta, MDM9150, MDM9205, MDM9206, MDM9607, MDM9650, MSM8905, MSM8909, MSM8917, MSM8920, MSM8937, MSM8940, MSM8953, MSM8996, MSM8996AU, MSM8998, Nicobar, QCM2150, QCS404, QCS405, QCS605, QCS610, QM215, Rennell, SA415M, SA515M, SA6155P, SC7180, SC8180X, SDA660, SDA845, SDM429, SDM429W, SDM439, SDM450, SDM630, SDM632, 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 · moderate confidence

An information disclosure vulnerability exists in the secure display-touch session tear-down process of multiple Qualcomm Snapdragon chipsets. The issue allows potential exposure of sensitive data during incomplete session cleanup when transitioning between secure display states. This affects processors across mobile, IoT, automotive, and infrastructure product lines.

MitigationApply security firmware updates provided by Qualcomm and distributed through device OEM patch cycles. Users should verify their devices are running the latest vendor-provided security patches.

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
Apq8009 FirmwareOperating system
Affected:all versions
Apq8017 FirmwareOperating system
Affected:all versions
Apq8053 FirmwareOperating system
Affected:all versions
Apq8076 FirmwareOperating system
Affected:all versions
Apq8096au FirmwareOperating system
Affected:all versions
Apq8098 FirmwareOperating system
Affected:all versions
Ipq6018 FirmwareOperating system
Affected:all versions
Kamorta 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
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

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
    Check the device's processor/chipset identification. On Linux/Android, examine /proc/cpuinfo or /sys/devices/soc0/soc_id. On automotive/IoT modules, check AT command responses or boot logs for the chipset identifier.
    Affected if The chipset matches one of the following: Apq8009, Apq8017, Apq8053, Apq8076, Apq8096au, Apq8098, Ipq6018, or Kamorta.
  2. Determine the firmware version
    Retrieve the firmware version from the device. On mobile devices, check Settings > About Phone > Build Number or via 'getprop' commands. On IoT/automotive modules, consult vendor documentation or query the modem/secure processor subsystem via diagnostic interfaces.
    Affected if All firmware versions of the listed chipsets are affected by this CVE.
  3. Confirm secure display-touch session capability
    Verify whether the device or module implements secure display and touch session handling. This feature is typically present in devices supporting secure UI, trusted execution environments, or mobile payment functionality. Check system logs (dmesg, logcat) for messages related to 'secure_display', 'trustedUI', or 'tee' (Trusted Execution Environment) initialization.
    Affected if The device implements and uses secure display-touch session functionality, which is required for this vulnerability to be exploitable.
  4. Check for incomplete session cleanup indicators
    Review system and secure processor logs for any anomalies during display state transitions, particularly when exiting secure UI modes or switching between secure display states. Look for warnings related to session termination or cleanup.
    Affected if The device transitions between secure display states and the firmware exhibits incomplete session cleanup behavior during these transitions.

A device is affected if it uses any of the listed Qualcomm chipsets (Apq8009, Apq8017, Apq8053, Apq8076, Apq8096au, Ipq6018, or Kamorta) and implements the secure display-touch session feature, since all firmware versions of these chipsets contain the vulnerability.

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 security firmware updates provided by Qualcomm and distributed through device OEM patch cycles. Users should verify their devices are running the latest vendor-provided security patches.

Fix this in Apq8009 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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