CVE-2021-30261: Possible integer and heap overflow due to lack of input command size validation while handling beacon template update command from HLOS in S
Noroxi assessment
Priority: Monitor (action score 31/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.16% (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
Possible integer and heap overflow due to lack of input command size validation while handling beacon template update command from HLOS in Snapdragon Auto, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables
- Published
- Sep 17, 2021
- Updated
- Jun 16, 2026
- EPSS
- 0.1% · 5th percentile
- CWE
- CWE-20
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.1%
CNA vs NVD score
- NVD
- 7.8
- CNA · qualcomm
- 8.4
- 0.6 point gap
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/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.
Running WordPress? Scan your site free with WP Lens
Noroxi 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 | apq8009 firmware | cpe:2.3:o:qualcomm:apq8009_firmware |
| qualcomm | apq8009 | cpe:2.3:h:qualcomm:apq8009 |
| qualcomm | apq8009w firmware | cpe:2.3:o:qualcomm:apq8009w_firmware |
| qualcomm | apq8009w | cpe:2.3:h:qualcomm:apq8009w |
| qualcomm | apq8017 firmware | cpe:2.3:o:qualcomm:apq8017_firmware |
| qualcomm | apq8017 | cpe:2.3:h:qualcomm:apq8017 |
| qualcomm | apq8037 firmware | cpe:2.3:o:qualcomm:apq8037_firmware |
| qualcomm | apq8037 | cpe:2.3:h:qualcomm:apq8037 |
| qualcomm | apq8053 firmware | cpe:2.3:o:qualcomm:apq8053_firmware |
| qualcomm | apq8053 | cpe:2.3:h:qualcomm:apq8053 |
| qualcomm | apq8084 firmware | cpe:2.3:o:qualcomm:apq8084_firmware |
| qualcomm | apq8084 | cpe:2.3:h:qualcomm:apq8084 |
and 188 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- qualcomm apq8009 firmwareall versions
- qualcomm apq8009w firmwareall versions
- qualcomm apq8017 firmwareall versions
- qualcomm apq8037 firmwareall versions
- qualcomm apq8053 firmwareall versions
- qualcomm apq8084 firmwareall versions
- qualcomm apq8096au firmwareall versions
- qualcomm aqt1000 firmwareall versions
- qualcomm ar6003 firmwareall versions
- qualcomm csr6030 firmwareall versions
- qualcomm csrb31024 firmwareall versions
- qualcomm mdm8207 firmwareall versions
- qualcomm mdm8215 firmwareall versions
- qualcomm mdm8215m firmwareall versions
- qualcomm mdm8615m firmwareall versions
- qualcomm mdm9150 firmwareall versions
- qualcomm mdm9205 firmwareall versions
- qualcomm mdm9206 firmwareall versions
- qualcomm mdm9207 firmwareall versions
- qualcomm mdm9215 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 Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables
- APQ8009, APQ8009W, APQ8016, APQ8017, APQ8037, APQ8052, APQ8053, APQ8056, APQ8076, MSM8108, MSM8208, MSM8209, MSM8608, MSM8909W, MSM8917, MSM8920, MSM8937, MSM8940, MSM8952, MSM8953, MSM8956, MSM8976, affected
Same product
qualcomm: all recordsOther highest-scoring records for the same primary product.
- CVE-2020-11261Memory corruption due to improper check to return error when user application requests memory allocation of a huge size in Snapdragon Auto, KEV61This week
- CVE-2021-1905Possible use after free due to improper handling of memory mapping of multiple processes simultaneously.KEV61This week
- CVE-2021-1906Improper handling of address deregistration on failure can lead to new GPU address allocation failure.KEV52Plan
Published before and after this one in the same product
- ← EarlierCVE-2021-1976Sep 17, 2021 · A use after free can occur due to improper validation of P2P device address in PD Request frame in Snapdragon Auto, Snapdragon Compute, Snap39Monitor
- ← EarlierCVE-2021-30260Sep 17, 2021 · Possible Integer overflow to buffer overflow issue can occur due to improper validation of input parameters when extscan hostlist configurat31Monitor
- Later →CVE-2020-11303Oct 20, 2021 · Accepting AMSDU frames with mismatched destination and source address can lead to information disclosure in Snapdragon Auto, Snapdragon Conn34Monitor
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.
No history yet (it accumulates with the daily EPSS job).
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)
CWE-20 · Improper Input ValidationCVSS 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.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Server Side Include (SSI) InjectionCAPEC-101likelihood: High · High
- Cross Zone ScriptingCAPEC-104likelihood: Medium · High
- Command Line Execution through SQL InjectionCAPEC-108likelihood: Low · Very High
- Object Relational Mapping InjectionCAPEC-109likelihood: Low · High
- SQL Injection through SOAP Parameter TamperingCAPEC-110likelihood: High · Very High
- Double EncodingCAPEC-120likelihood: Low · Medium
- Subverting Environment Variable ValuesCAPEC-13likelihood: High · Very High
ATT&CK techniques
- Obfuscated Files or InformationT1027
- Masquerading: Invalid Code SignatureT1036.001
- Steal Web Session CookieT1539
- Subvert Trust Controls: Code SigningT1553.002
- Impair Defenses:Impair Command History LoggingT1562.003
- Hijack Execution Flow:Dynamic Linker HijackingT1574.006
- Hijack Execution Flow:Path Interception by PATH Environment VariableT1574.007
Change log
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.