LiveActive security incident?Get immediate response
CVE Record

CVE-2020-11199: HLOS to access EL3 stack canary by just mapping imem region due to Improper access control and can lead to...

HLOS to access EL3 stack canary by just mapping imem region due to Improper access control and can lead to information exposure in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2020-11199 is an information exposure issue in many Qualcomm Snapdragon product lines. The main operating system could access an EL3 stack canary by mapping an IMEM region, weakening a low-level firmware protection. The provided sources do not include CVSS scoring, named fixes, or evidence of active exploitation.

Executive priority

Treat this as a firmware supply-chain exposure requiring inventory and vendor follow-up, not an emergency based on the provided evidence. Prioritize high-value or long-lived embedded devices because remediation depends on OEM firmware availability.

Technical view

The issue is improper access control between HLOS and EL3-protected data. Qualcomm describes HLOS access to the EL3 stack canary through IMEM region mapping, causing information exposure across Snapdragon Auto, Compute, Connectivity, IoT, Mobile, Wearables, Voice & Music, and networking platforms.

Likely exposure

Exposure is most likely in products built on the listed Qualcomm Snapdragon chipsets and PMICs. Practical risk depends on the device OEM, firmware branch, boot chain, and whether Qualcomm March 2021 security bulletin fixes were integrated into shipped firmware.

Exploitation context

The source bundle does not show KEV listing, public exploitation, exploit code, or in-the-wild attacks. The described impact is information exposure, potentially useful for weakening firmware-level protections, but public evidence here is insufficient to claim weaponized exploitation.

Researcher notes

Evidence is limited to CVE metadata and Qualcomm’s bulletin reference. No CVSS, CWE, patch diff, or exploit status is included. Focus research on affected platform confirmation, OEM firmware lineage, and whether IMEM access controls were corrected in the deployed firmware branch.

Mitigation direction

  • Review Qualcomm’s March 2021 security bulletin and affected chipset list.
  • Obtain firmware or BSP updates from the device OEM or Qualcomm channel.
  • Prioritize devices using listed Snapdragon platforms in sensitive environments.
  • Confirm vendor guidance before assuming a fixed firmware version.
  • Retire or isolate unsupported devices if no vendor update exists.

Validation and detection

  • Inventory hardware models and map them to Qualcomm part numbers.
  • Check OEM security bulletins for CVE-2020-11199 remediation status.
  • Verify deployed firmware includes March 2021 Qualcomm security fixes where applicable.
  • Document devices with unsupported or unknown firmware provenance.
  • Track exceptions for embedded, IoT, automotive, and networking equipment.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2020-11199 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Qualcomm, Inc.Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and NetworkingAPQ8009, APQ8017, APQ8037, APQ8053, APQ8064AU, APQ8096AU, AQT1000, AR8031, AR8035, AR8151, CSR8811, CSRA6620, CSRA6640, CSRB31024, FSM10055, FSM10056, IPQ6000, IPQ6005, IPQ6010, IPQ6018, IPQ6028, IPQ8070, IPQ8070A, IPQ8071, IPQ8071A, IPQ8072, IPQ8072A, IPQ8074, IPQ8074A, IPQ8076, IPQ8076A, IPQ8078, IPQ8078A, IPQ8173, IPQ8174, MDM8207, MDM9150, MDM9205, MDM9206, MDM9207, MDM9250, MDM9607, MDM9628, MDM9640, MDM9650, MDM9655, MSM8108, MSM8208, MSM8209, MSM8608, MSM8917, MSM8920, MSM8937, MSM8940, MSM8953, MSM8996AU, PM215, PM3003A, PM4125, PM4250, PM439, PM456, PM6125, PM6150, PM6150A, PM6150L, PM6250, PM6350, PM640A, PM640L, PM640P, PM660, PM660A, PM660L, PM670, PM670A, PM670L, PM7150A, PM7150L, PM7250, PM7250B, PM8004, PM8005, PM8008, PM8009, PM8019, PM8150, PM8150A, PM8150B, PM8150C, PM8150L, PM8250, PM8350, PM855, PM855A, PM855B, PM855L, PM855P, PM8909, PM8916, PM8937, PM8940, PM8953, PM8996, PM8998, PMC1000H, PMD9607, PMD9655, PMD9655AU, PME605, PMI632, PMI8937, PMI8940, PMI8952, PMI8994, PM ...[truncated*]Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.