u'XBL SEC clears only ZI region when loading Qualcomm-signed segments can lead to improper access issue' in Snapdragon Compute, Snapdragon C
u'XBL SEC clears only ZI region when loading Qualcomm-signed segments can lead to improper access issue' in Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wired Infrastructure and Networking in APQ8098, Kamorta, MSM8998, QCS404, QCS605, SDA660, SDA845, SDM630, SDM636, SDM660, SDM670, SDM710, SDM845, SDM850, SXR1130
- Published
- Sep 8, 2020
- Updated
- Jun 16, 2026
- EPSS
- 0.2% · 10th percentile
- CWE
- —
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| qualcomm | apq8098 firmware | cpe:2.3:o:qualcomm:apq8098_firmware |
| qualcomm | apq8098 | cpe:2.3:h:qualcomm:apq8098 |
| qualcomm | kamorta firmware | cpe:2.3:o:qualcomm:kamorta_firmware |
| qualcomm | kamorta | cpe:2.3:h:qualcomm:kamorta |
| qualcomm | msm8998 firmware | cpe:2.3:o:qualcomm:msm8998_firmware |
| qualcomm | msm8998 | cpe:2.3:h:qualcomm:msm8998 |
| qualcomm | qcs404 firmware | cpe:2.3:o:qualcomm:qcs404_firmware |
| qualcomm | qcs404 | cpe:2.3:h:qualcomm:qcs404 |
| qualcomm | qcs605 firmware | cpe:2.3:o:qualcomm:qcs605_firmware |
| qualcomm | qcs605 | cpe:2.3:h:qualcomm:qcs605 |
| qualcomm | sda660 firmware | cpe:2.3:o:qualcomm:sda660_firmware |
| qualcomm | sda660 | cpe:2.3:h:qualcomm:sda660 |
and 18 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- qualcomm apq8098 firmwareall versions
- qualcomm kamorta firmwareall versions
- qualcomm msm8998 firmwareall versions
- qualcomm qcs404 firmwareall versions
- qualcomm qcs605 firmwareall versions
- qualcomm sda660 firmwareall versions
- qualcomm sda845 firmwareall versions
- qualcomm sdm630 firmwareall versions
- qualcomm sdm636 firmwareall versions
- qualcomm sdm660 firmwareall versions
- qualcomm sdm670 firmwareall versions
- qualcomm sdm710 firmwareall versions
- qualcomm sdm845 firmwareall versions
- qualcomm sdm850 firmwareall versions
- qualcomm sxr1130 firmwareall versions
Versions reported by the vendor
Affected version ranges reported by the assigning authority (qualcomm). Independent of NVD's CPE analysis and usually ahead of it.
Qualcomm, Inc. Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wired Infrastructure and Networking
- APQ8098, Kamorta, MSM8998, QCS404, QCS605, SDA660, SDA845, SDM630, SDM636, SDM660, SDM670, SDM710, SDM845, SDM850, SXR1130affected
Same product
qualcomm: all recordsOther highest-scoring records for the same primary product.
- CVE-2020-3669u'Buffer Overflow issue in WLAN tcp ip verification due to usage of out of range pointer offset' in Snapdragon Auto, Snapdragon Compute, Sna39Monitor
- CVE-2020-3667u'Buffer Overflow in mic calculation for WPA due to copying data into buffer without validating the length of buffer' in Snapdragon Auto, Sn39Monitor
- CVE-2019-14112Potential buffer overflow while processing CBF frames due to lack of check of buffer length before copy in Snapdragon Auto, Snapdragon Compu39Monitor
- CVE-2019-14086Possible integer overflow while checking the length of frame which is a 32 bit integer and is added to another 32 bit integer which can lead39Monitor
- CVE-2020-11206Possible buffer overflow in Fastrpc while handling received parameters due to lack of validation on input parameters' in Snapdragon Auto, Sn32Monitor
- CVE-2019-10628u'Memory can be potentially corrupted if random index is allowed to manipulate TLB entries in Kernel from user library' in Snapdragon Auto, 31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
- www.qualcomm.com/company/product-security/bulletins/august-2020-bulletin
- www.qualcomm.com/company/product-security/bulletins/august-2020-security-bulletin
Vendor advisories and official records. Exploit/PoC links are deliberately left out.