u'Improper access control can lead signed process to guess pid of other processes and access their address space' in Snapdragon Auto, Snapdr
u'Improper access control can lead signed process to guess pid of other processes and access their address space' in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wired Infrastructure and Networking in Bitra, Nicobar, QCS605, QCS610, Rennell, SA6155P, Saipan, SC7180, SC8180X, SDM670, SDM710, SDM845, SDM850, SM6150, SM7150, SM8150, SM8250, SXR1130, SXR2130
- Published
- Sep 8, 2020
- Updated
- Jun 16, 2026
- EPSS
- 0.2% · 9th 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 | bitra firmware | cpe:2.3:o:qualcomm:bitra_firmware |
| qualcomm | bitra | cpe:2.3:h:qualcomm:bitra |
| qualcomm | nicobar firmware | cpe:2.3:o:qualcomm:nicobar_firmware |
| qualcomm | nicobar | cpe:2.3:h:qualcomm:nicobar |
| qualcomm | qcs605 firmware | cpe:2.3:o:qualcomm:qcs605_firmware |
| qualcomm | qcs605 | cpe:2.3:h:qualcomm:qcs605 |
| qualcomm | qcs610 firmware | cpe:2.3:o:qualcomm:qcs610_firmware |
| qualcomm | qcs610 | cpe:2.3:h:qualcomm:qcs610 |
| qualcomm | rennell firmware | cpe:2.3:o:qualcomm:rennell_firmware |
| qualcomm | rennell | cpe:2.3:h:qualcomm:rennell |
| qualcomm | sa6155p firmware | cpe:2.3:o:qualcomm:sa6155p_firmware |
| qualcomm | sa6155p | cpe:2.3:h:qualcomm:sa6155p |
and 26 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- qualcomm bitra firmwareall versions
- qualcomm nicobar firmwareall versions
- qualcomm qcs605 firmwareall versions
- qualcomm qcs610 firmwareall versions
- qualcomm rennell firmwareall versions
- qualcomm sa6155p firmwareall versions
- qualcomm saipan firmwareall versions
- qualcomm sc7180 firmwareall versions
- qualcomm sc8180x firmwareall versions
- qualcomm sdm670 firmwareall versions
- qualcomm sdm710 firmwareall versions
- qualcomm sdm845 firmwareall versions
- qualcomm sdm850 firmwareall versions
- qualcomm sm6150 firmwareall versions
- qualcomm sm7150 firmwareall versions
- qualcomm sm8150 firmwareall versions
- qualcomm sm8250 firmwareall versions
- qualcomm sxr1130 firmwareall versions
- qualcomm sxr2130 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 Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wired Infrastructure and Networking
- Bitra, Nicobar, QCS605, QCS610, Rennell, SA6155P, Saipan, SC7180, SC8180X, SDM670, SDM710, SDM845, SDM850, SM6150, SM7150, SM8150, SM8250, SXR1130, SXR2130affected
Same product
qualcomm: all recordsOther highest-scoring records for the same primary product.
- CVE-2020-3694u'Use out of range pointer issue can occur due to incorrect buffer range check during the execution of qseecom' in Snapdragon Auto, Snapdrag31Monitor
- CVE-2020-11129u'During the error occurrence in capture request, the buffer is freed and later accessed causing the camera APP to fail due to memory use-af31Monitor
- CVE-2020-3646u'Buffer overflow seen as the destination buffer size is lesser than the source buffer size in video application' in Snapdragon Compute, Sna31Monitor
- CVE-2020-3640u'Resizing the usage table header before passing all the checks leads to the function exiting with a usage table in invalid state when a HLO31Monitor
- CVE-2020-3629u'Stack out of bound issue occurs when making query to DSP capabilities due to wrong assumption was made on determining the buffer size for 31Monitor
- CVE-2019-14117u'Whenever the page list is updated via privileged user, the previous list elements are freed but are not deleted from the list which result31Monitor
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.