LiveActive security incident?Get immediate response
CVE Record

CVE-2020-3657: u'Remote code execution can happen by sending a carefully crafted POST query when Device configuration is a...

u'Remote code execution can happen by sending a carefully crafted POST query when Device configuration is accessed from a tethered client through webserver due to lack of array bound check.' in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking in APQ8009, APQ8017, APQ8053, APQ8096AU, APQ8098, IPQ4019, IPQ6018, IPQ8064, IPQ8074, MDM9150, MDM9206, MDM9207C, MDM9607, MDM9640, MDM9650, MSM8905, MSM8909W, MSM8953, MSM8996AU, QCA6574AU, QCS405, QCS610, QRB5165, SC8180X, SDA660, SDA845, SDM429, SDM429W, SDM630, SDM632, SDM636, SDM660, SDM845, SDX20, SDX24, SDX55, SM8250

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2020-3657 is a Qualcomm Snapdragon device-configuration webserver flaw. When a tethered client accesses device configuration, a crafted POST request can trigger remote code execution because the software lacks an array bounds check. Exposure depends on whether products include the listed chipsets and expose that tethered configuration path.

Executive priority

Treat as a high-priority asset inventory and firmware governance issue where affected Snapdragon-based devices are deployed. Business urgency is highest for managed fleets, networking devices, IoT deployments, and products where tethered configuration access is practical.

Technical view

The CVE describes missing array bounds checking in a webserver path used for device configuration from a tethered client. A crafted POST query may lead to remote code execution. Qualcomm lists affected Snapdragon families across mobile, IoT, auto, compute, networking, wearables, wired infrastructure, and voice/music products.

Likely exposure

Organizations may be exposed through devices using the listed Qualcomm chipsets, especially embedded, IoT, networking, mobile, automotive, or wearable products that allow tethered client access to device configuration via the affected webserver component.

Exploitation context

The provided sources do not show CISA KEV listing, confirmed active exploitation, public exploit availability, or attack prevalence. The documented condition requires tethered client access to the device configuration webserver and a crafted POST query.

Researcher notes

Evidence is limited to the CVE description and Qualcomm bulletin reference. No CVSS, CWE, fixed version details, or exploitation confirmation are included in the provided bundle. Avoid assuming internet-reachable attack surface without validating the tethered-client configuration path.

Mitigation direction

  • Identify devices using the listed Qualcomm Snapdragon chipsets.
  • Check Qualcomm and device OEM advisories for firmware updates.
  • Prioritize devices exposing tethered configuration workflows.
  • Restrict untrusted physical or tethered client access where feasible.
  • Track vendor remediation status for embedded and managed fleets.

Validation and detection

  • Inventory affected chipset models across mobile, IoT, networking, and embedded assets.
  • Confirm whether device configuration is reachable from tethered clients.
  • Review OEM firmware versions against vendor security bulletins.
  • Check vulnerability management records for CVE-2020-3657 coverage.
  • Document devices lacking available vendor remediation guidance.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-3657 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Qualcomm, Inc.Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and NetworkingAPQ8009, APQ8017, APQ8053, APQ8096AU, APQ8098, IPQ4019, IPQ6018, IPQ8064, IPQ8074, MDM9150, MDM9206, MDM9207C, MDM9607, MDM9640, MDM9650, MSM8905, MSM8909W, MSM8953, MSM8996AU, QCA6574AU, QCS405, QCS610, QRB5165, SC8180X, SDA660, SDA845, SDM429, SDM429W, SDM630, SDM632, SDM636, SDM660, SDM845, SDX20, SDX24, SDX55, SM8250Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.