CVE-2021-35079: Improper validation of permissions for third party application accessing Telephony service API can lead to information disclosure in…
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.13% (FIRST EPSS).
- 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.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Improper validation of permissions for third party application accessing Telephony service API can lead to information disclosure in Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile
- Published
- Jun 14, 2022
- Updated
- Jun 16, 2026
- EPSS
- 0.1% · 2th percentile
- CWE
- CWE-281
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- 5.5
- CNA · qualcomm
- 6.2
- 0.7 point gap
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| qualcomm | apq8053 firmware | cpe:2.3:o:qualcomm:apq8053_firmware |
| qualcomm | apq8053 | cpe:2.3:h:qualcomm:apq8053 |
| qualcomm | aqt1000 firmware | cpe:2.3:o:qualcomm:aqt1000_firmware |
| qualcomm | aqt1000 | cpe:2.3:h:qualcomm:aqt1000 |
| qualcomm | msm8953 firmware | cpe:2.3:o:qualcomm:msm8953_firmware |
| qualcomm | msm8953 | cpe:2.3:h:qualcomm:msm8953 |
| qualcomm | qca6390 firmware | cpe:2.3:o:qualcomm:qca6390_firmware |
| qualcomm | qca6390 | cpe:2.3:h:qualcomm:qca6390 |
| qualcomm | qca6391 firmware | cpe:2.3:o:qualcomm:qca6391_firmware |
| qualcomm | qca6391 | cpe:2.3:h:qualcomm:qca6391 |
| qualcomm | qca6420 firmware | cpe:2.3:o:qualcomm:qca6420_firmware |
| qualcomm | qca6420 | cpe:2.3:h:qualcomm:qca6420 |
and 110 more
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 Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile
- APQ8053, AQT1000, MSM8953, QCA6390, QCA6391, QCA6420, QCA6426, QCA6430, QCA6436, QCM4290, QCS4290, QCS603, QCS605, Qualcomm215, SD460, SD480, SD662, SD680, SD690 5G, SD695, SD750G, SD765, SD765G, SD76affected
Affected versions · NVD (20)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- qualcomm apq8053 firmwareall versions
- qualcomm aqt1000 firmwareall versions
- qualcomm msm8953 firmwareall versions
- qualcomm qca6390 firmwareall versions
- qualcomm qca6391 firmwareall versions
- qualcomm qca6420 firmwareall versions
- qualcomm qca6426 firmwareall versions
- qualcomm qca6430 firmwareall versions
- qualcomm qca6436 firmwareall versions
- qualcomm qcm4290 firmwareall versions
- qualcomm qcs4290 firmwareall versions
- qualcomm qcs603 firmwareall versions
- qualcomm qcs605 firmwareall versions
- qualcomm qualcomm215 firmwareall versions
- qualcomm sd460 firmwareall versions
- qualcomm sd480 firmwareall versions
- qualcomm sd662 firmwareall versions
- qualcomm sd680 firmwareall versions
- qualcomm sd690 5g firmwareall versions
- qualcomm sd695 firmwareall versions
Same product
qualcomm: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-22071Possible use after free when process shell memory is freed using IOCTL munmap call and process initialization is in progress in Snapdragon…KEV61This week
- CVE-2020-11264Improper authentication of Non-EAPOL/WAPI plaintext frames during four-way handshake can lead to arbitrary network packet injection in…43Plan
- CVE-2020-11153u'Out of bound memory access while processing GATT data received due to lack of check of pdu data length and leads to remote code…40Plan
Published before and after this one in the same product
- ← EarlierCVE-2021-30312Oct 20, 2021 · Improper authentication of sub-frames of a multicast AMSDU frame can lead to information disclosure in Snapdragon Auto, Snapdragon Compute…30Monitor
- ← EarlierCVE-2021-30265Nov 12, 2021 · Possible memory corruption due to improper validation of memory address while processing user-space IOCTL for clearing Filter and Route…26Monitor
- Later →CVE-2021-35092Jun 14, 2022 · Processing DCB/AVB algorithm with an invalid queue index from IOCTL request could lead to arbitrary address modification in Snapdragon…26Monitor
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.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
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
- none
- Availability
- none
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-281 · Improper Preservation of PermissionsCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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.
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.