Skip to content
Sign in
CVE-2020-3699Not scoredCWE-120

CVE-2020-3699: Qualcomm, Inc. Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer Electronics Connectivi… vulnerability

Qualcomm, Inc. · Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer Electronics Connectivi…

Affected: Qualcomm, Inc. Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer Electronics Connectivi… · Exploitation: unlikely (under 1%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

0.9%probability of exploitation in the next 30 days
60th percentile
050100

Higher than 60% of scored CVEs

Not scored yet. The CVE record carries no CVSS score.

DescriptionCVE.org

Possible out of bound access while processing assoc response from host due to improper length check before copying into buffer in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables in APQ8009, APQ8017, APQ8053, APQ8096AU, MDM9206, MDM9207C, MDM9607, MDM9640, MDM9650, MSM8905, MSM8909W, MSM8917, MSM8920, MSM8937, MSM8940, MSM8953, MSM8996AU, Nicobar, QCA6174A, QCA6574AU, QCA9377, QCA9379, QCM2150, QCN7605, QCS405, QCS605, QM215, SA6155P, Saipan, SC8180X, SDA845, SDM429, SDM429W, SDM439, SDM450, SDM630, SDM632, SDM636, SDM660, SDM845, SDX20, SDX55, SM6150, SM7150, SM8150, SM8250, SXR2130

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

  • Qualcomm, Inc. · Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon…APQ8009, APQ8017, APQ8053, APQ8096AU, MDM9206, MDM9207C, MD…

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas
Exploitation
Unlikely (under 1%). EPSS under 1%, or no score yet.
CISA KEV
Not listed
Public check
No public nuclei template
Published
July 2020

CoverageNo articles yet

No CyberSIXT article names CVE-2020-3699 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.

References

Updated AboutDevelopersSign in