CVE-2020-3673· NVD / CVE Program· CNA qualcomm

u'Buffer overflow can happen as part of SIP message packet processing while storing values in array due to lack of check to validate the ind

Noroxi assessment

Priority: Monitor (action score 39/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: 1% (FIRST EPSS); higher than 64.3% of all records.
Anyone who can reach it over the internet can trigger it. No account or password is required. 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

u'Buffer overflow can happen as part of SIP message packet processing while storing values in array due to lack of check to validate the index length' in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables in Agatti, APQ8053, APQ8096AU, APQ8098, Bitra, Kamorta, MSM8905, MSM8909W, MSM8917, MSM8940, MSM8953, MSM8996AU, Nicobar, QCA6390, QCA6574AU, QCM2150, QCS605, QM215, Rennell, SA6155P, SA8155P, Saipan, SDA660, SDM429, SDM429W, SDM439, SDM450, SDM630, SDM632, SDM636, SDM660, SDM670, SDM710, SDM845, SM6150, SM7150, SM8150, SM8250, SXR1130, SXR2130

CriticalCVSS 9.8 · v3.1—No exploit No fix recorded

Pre-auth

Published: Nov 2, 2020
Updated: Jun 16, 2026
EPSS: 1.0% · 64th percentile
CWE: CWE-129

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 39 / 40 · 9.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 1.0%

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

Is your version affected? Check it

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 help

Affected 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	agatti firmware	cpe:2.3:o:qualcomm:agatti_firmware
qualcomm	agatti	cpe:2.3:h:qualcomm:agatti
qualcomm	apq8053 firmware	cpe:2.3:o:qualcomm:apq8053_firmware
qualcomm	apq8053	cpe:2.3:h:qualcomm:apq8053
qualcomm	apq8096au firmware	cpe:2.3:o:qualcomm:apq8096au_firmware
qualcomm	apq8096au	cpe:2.3:h:qualcomm:apq8096au
qualcomm	apq8098 firmware	cpe:2.3:o:qualcomm:apq8098_firmware
qualcomm	apq8098	cpe:2.3:h:qualcomm:apq8098
qualcomm	bitra firmware	cpe:2.3:o:qualcomm:bitra_firmware
qualcomm	bitra	cpe:2.3:h:qualcomm:bitra
qualcomm	kamorta firmware	cpe:2.3:o:qualcomm:kamorta_firmware
qualcomm	kamorta	cpe:2.3:h:qualcomm:kamorta

and 68 more

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

qualcomm agatti firmwareall versions
qualcomm apq8053 firmwareall versions
qualcomm apq8096au firmwareall versions
qualcomm apq8098 firmwareall versions
qualcomm bitra firmwareall versions
qualcomm kamorta firmwareall versions
qualcomm msm8905 firmwareall versions
qualcomm msm8909w firmwareall versions
qualcomm msm8917 firmwareall versions
qualcomm msm8940 firmwareall versions
qualcomm msm8953 firmwareall versions
qualcomm msm8996au firmwareall versions
qualcomm nicobar firmwareall versions
qualcomm qca6390 firmwareall versions
qualcomm qca6574au firmwareall versions
qualcomm qcm2150 firmwareall versions
qualcomm qcs605 firmwareall versions
qualcomm qm215 firmwareall versions
qualcomm rennell firmwareall versions
qualcomm sa6155p 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 Wearables
- Agatti, APQ8053, APQ8096AU, APQ8098, Bitra, Kamorta, MSM8905, MSM8909W, MSM8917, MSM8940, MSM8953, MSM8996AU, Nicobar, QCA6390, QCA6574AU, QCM2150, QCS605, QM215, Rennell, SA6155P, SA8155P, Saipan, SDaffected

Same product

qualcomm: all records

Other highest-scoring records for the same primary product.

CVE-2020-3692u'Possible buffer overflow while updating output buffer for IMEI and Gateway Address due to lack of check of input validation for parameters
39Monitor
CVE-2020-3654u'Buffer overflow occurs while processing SIP message packet due to lack of check of index validation before copying into it' in Snapdragon
39Monitor
CVE-2020-3670u'Potential out of bounds read while processing downlink NAS transport message due to improper length check of Information Element(IEI) NAS
36Monitor

Published before and after this one in the same product

← EarlierCVE-2020-11174Nov 2, 2020 · u'Array index underflow issue in adsp driver due to improper check of channel id before used as array index.' in Snapdragon Auto, Snapdragon
31Monitor
← EarlierCVE-2020-3638Nov 2, 2020 · u'An Unaligned address or size can propagate to the database due to improper page permissions and can lead to improper access control' in Sn
31Monitor
Later →CVE-2020-3678Nov 2, 2020 · u'A buffer overflow could occur if the API is improperly used due to UIE init does not contain a buffer size a param' in Snapdragon Consumer
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.

EPSS, last 120 days

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 researchers

Finders, 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).