LiveActive security incident?Get immediate response
CVE Record

CVE-2020-11228: Part of RPM region was not protected from xblSec itself due to improper policy and leads to unprivileged ac...

Part of RPM region was not protected from xblSec itself due to improper policy and leads to unprivileged access in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wired Infrastructure and Networking

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2020-11228 is a Qualcomm Snapdragon platform vulnerability where a protected resource area was not fully protected because of an improper policy. The source says this can lead to unprivileged access. Business urgency depends on whether your phones, IoT, automotive, compute, networking, or embedded products use the listed Snapdragon components.

Executive priority

Treat this as an inventory and supplier-risk item rather than a confirmed emergency. Prioritize fleets with Qualcomm-based embedded devices, especially long-lived IoT, automotive, and networking equipment where firmware updates are slow or vendor-dependent.

Technical view

The CVE describes part of the RPM region not being protected from xblSec itself due to improper policy, resulting in unprivileged access. Qualcomm lists broad Snapdragon product families and many component identifiers. The provided sources do not include CVSS, attack vector, exploit prerequisites, or detailed remediation text.

Likely exposure

Exposure is likely tied to devices or products using affected Qualcomm Snapdragon chipsets or listed power/connectivity components. Software-only asset inventories may miss this; hardware bills of materials, OEM firmware records, and device security bulletin levels are needed.

Exploitation context

The source bundle does not show CISA KEV listing, public exploitation, exploit maturity, or proof-of-concept availability. Do not treat this as actively exploited based on the provided evidence.

Researcher notes

Key gaps are CVSS, CWE, attack vector, affected firmware versions, and concrete fix identifiers. The only technical root cause provided is improper policy protecting the RPM region from xblSec. Further analysis should stay anchored to Qualcomm and OEM advisories.

Mitigation direction

  • Review Qualcomm’s March 2021 security bulletin for vendor-specific guidance.
  • Identify OEM firmware or security updates for affected Snapdragon-based products.
  • Prioritize managed mobile, IoT, automotive, and networking devices using listed components.
  • Ask suppliers for written applicability and remediation status.
  • Plan compensating controls for unsupported or unpatchable embedded devices.

Validation and detection

  • Compare hardware inventory and BOMs against Qualcomm’s affected component list.
  • Check OEM firmware versions and security bulletin levels on deployed devices.
  • Confirm whether each affected product received Qualcomm-derived fixes from its OEM.
  • Document devices where applicability is unknown or vendor support has ended.
  • Track exceptions until supplier confirmation or replacement is complete.
Prepared
Confidence
medium
Sources
3

Public sources used

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-11228 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.

Source materials

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 Mobile, Snapdragon Wired Infrastructure and NetworkingAQT1000, AR8035, PM3003A, PM4125, PM4250, PM6125, PM6150, PM6150A, PM6150L, PM6350, PM640A, PM640L, PM640P, PM7150A, PM7150L, PM7250, PM7250B, PM8004, PM8005, PM8008, PM8009, PM8150, PM8150A, PM8150B, PM8150C, PM8150L, PM8250, PM8350, PM855, PM855B, PM855L, PM855P, PM8998, PMC1000H, PMD9655, PMI632, PMI8998, PMK8002, PMK8003, PMM8195AU, PMM855AU, PMR525, PMR735A, PMR735B, PMX24, PMX55, QAT3516, QAT3518, QAT3519, QAT3522, QAT3550, QAT3555, QAT5515, QAT5516, QAT5522, QAT5533, QBT1500, QBT2000, QCA6390, QCA6391, QCA6420, QCA6421, QCA6426, QCA6430, QCA6431, QCA6436, QCA6574A, QCA6574AU, QCA6584AU, QCA6595, QCA6595AU, QCA6696, QCA8337, QCA9984, QCM2290, QCM4290, QCS2290, QCS405, QCS4290, QDM2301, QDM2302, QDM2305, QDM2307, QDM2308, QDM2310, QDM3301, QDM5620, QDM5621, QDM5650, QDM5652, QDM5670, QDM5671, QDM5677, QDM5679, QET4101, QET5100, QET6100, QET6110, QFS2530, QFS2580, QLN4642, QLN4650, QLN5020, QLN5030, QLN5040, QPA2625, QPA4360, QPA4361, QPA5460, QPA5580, QPA5581, QPA6560, QPA8673, QPA8686, Q ...[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.