CVE-2020-3646: u'Buffer overflow seen as the destination buffer size is lesser than the source buffer size in video application' in Snapdragon Compute…
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.21% (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.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
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
u'Buffer overflow seen as the destination buffer size is lesser than the source buffer size in video application' in Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables in Bitra, MSM8909W, QCM2150, QCS405, QCS605, Saipan, SC8180X, SDA845, SDM429W, SDX24, SDX55, SM6150, SM7150, SM8150, SM8250, SXR2130
- Published
- Sep 8, 2020
- Updated
- Jun 16, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- CWE-120
Report tools
Action score
31
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
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 | bitra firmware | cpe:2.3:o:qualcomm:bitra_firmware |
| qualcomm | bitra | cpe:2.3:h:qualcomm:bitra |
| qualcomm | msm8909w firmware | cpe:2.3:o:qualcomm:msm8909w_firmware |
| qualcomm | msm8909w | cpe:2.3:h:qualcomm:msm8909w |
| qualcomm | qcm2150 firmware | cpe:2.3:o:qualcomm:qcm2150_firmware |
| qualcomm | qcm2150 | cpe:2.3:h:qualcomm:qcm2150 |
| qualcomm | qcs405 firmware | cpe:2.3:o:qualcomm:qcs405_firmware |
| qualcomm | qcs405 | cpe:2.3:h:qualcomm:qcs405 |
| qualcomm | qcs605 firmware | cpe:2.3:o:qualcomm:qcs605_firmware |
| qualcomm | qcs605 | cpe:2.3:h:qualcomm:qcs605 |
| qualcomm | saipan firmware | cpe:2.3:o:qualcomm:saipan_firmware |
| qualcomm | saipan | cpe:2.3:h:qualcomm:saipan |
and 20 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 Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables
- Bitra, MSM8909W, QCM2150, QCS405, QCS605, Saipan, SC8180X, SDA845, SDM429W, SDX24, SDX55, SM6150, SM7150, SM8150, SM8250, SXR2130affected
Affected versions · NVD (16)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- qualcomm bitra firmwareall versions
- qualcomm msm8909w firmwareall versions
- qualcomm qcm2150 firmwareall versions
- qualcomm qcs405 firmwareall versions
- qualcomm qcs605 firmwareall versions
- qualcomm saipan firmwareall versions
- qualcomm sc8180x firmwareall versions
- qualcomm sda845 firmwareall versions
- qualcomm sdm429w firmwareall versions
- qualcomm sdx24 firmwareall versions
- qualcomm sdx55 firmwareall versions
- qualcomm sm6150 firmwareall versions
- qualcomm sm7150 firmwareall versions
- qualcomm sm8150 firmwareall versions
- qualcomm sm8250 firmwareall versions
- qualcomm sxr2130 firmwareall versions
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…31Monitor
- 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…31Monitor
- 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…31Monitor
Published before and after this one in the same product
- ← EarlierCVE-2019-14117Sep 8, 2020 · u'Whenever the page list is updated via privileged user, the previous list elements are freed but are not deleted from the list which…31Monitor
- ← EarlierCVE-2020-3629Sep 8, 2020 · u'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
- Later →CVE-2020-3679Sep 9, 2020 · u'During execution after Address Space Layout Randomization is turned on for QTEE, part of code is still mapped at known address including…22Monitor
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.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-20-691 · Sep 9, 2020(Qualcomm Snapdragon Zafiyetleri)
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
- 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-120 · Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
When data is copied, the source length is not compared with the size of the destination buffer. Excess data overwrites adjacent memory.
The bug in code
The whole CWE-120 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
char buf[256];
memcpy(buf, pkt->data, pkt->len);Fixed
char buf[256];
if (pkt->len > sizeof(buf)) {
return -EINVAL;
}
memcpy(buf, pkt->data, pkt->len);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
- Overflow BuffersCAPEC-100likelihood: High · Very High
- Client-side Injection-induced Buffer OverflowCAPEC-14likelihood: Medium · High
- Filter Failure through Buffer OverflowCAPEC-24likelihood: High · High
- MIME ConversionCAPEC-42likelihood: High · High
- Overflow Binary Resource FileCAPEC-44likelihood: High · Very High
- Buffer Overflow via Symbolic LinksCAPEC-45likelihood: High · High
- Overflow Variables and TagsCAPEC-46likelihood: High · High
ATT&CK techniques
—
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.