dbcve.org
Agatti FirmwareOperating system · Qualcomm

CVE-2020-3654

CRITICAL · 9.8 CVSS v3.1 Published 2020-11-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
u'Buffer overflow occurs while processing SIP message packet due to lack of check of index validation before copying into it' 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, MSM8998, 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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A buffer overflow vulnerability exists in the SIP message processing component of Qualcomm Snapdragon chipsets. The vulnerability stems from missing index validation checks before copying data into a buffer, allowing an attacker to overwrite adjacent memory by sending specially crafted SIP packets. This remote code execution vulnerability affects multiple chipset families used in mobile devices, wearables, IoT devices, and automotive systems.

MitigationApply vendor-supplied firmware patches from Qualcomm and device OEMs. As an interim control, implement network-level filtering of SIP traffic at perimeter firewalls to block malformed SIP messages before they reach affected devices.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Agatti FirmwareOperating system
Affected:all versions
Apq8053 FirmwareOperating system
Affected:all versions
Apq8096au FirmwareOperating system
Affected:all versions
Apq8098 FirmwareOperating system
Affected:all versions
Bitra FirmwareOperating system
Affected:all versions
Kamorta FirmwareOperating system
Affected:all versions
Msm8905 FirmwareOperating system
Affected:all versions
Msm8909w FirmwareOperating system
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Qualcomm chipset model
    On Android devices, run 'cat /proc/cpuinfo' or check 'Settings > About Phone > Chipset' to identify the exact Qualcomm processor. On IoT/automotive devices, check the hardware specifications or device documentation.
    Affected if The chipset matches one of the affected models: Agatti, Apq8053, Apq8096au, Apq8098, Bitra, Kamorta, Msm8905, or Msm8909w.
  2. Check the installed firmware version
    Access the device's firmware information through manufacturer diagnostics, bootloader interface, or system information menus. Query 'getprop ro.build.version.security_patch' or check 'Settings > About Phone > Build Number' for Android devices.
    Affected if The firmware version cannot be updated to a vendor patch, indicating the device remains on an affected baseline.
  3. Verify if SIP/VoIP functionality is enabled
    Check device settings for SIP calling, VoIP apps, or telephony configurations. On Android, look under 'Settings > Connections > Wi-Fi Calling' or examine running processes for SIP-related services.
    Affected if SIP calling or VoIP features are enabled and the device processes incoming SIP traffic.
  4. Inspect network exposure of SIP services
    Use network scanning tools (nmap, netstat) to identify if UDP/TCP ports 5060 or 5061 (SIP ports) are listening and exposed on the device or network perimeter.
    Affected if The device has SIP ports open and accessible, making it reachable by crafted SIP packets.
  5. Review SIP traffic at the network perimeter
    Capture and inspect SIP traffic using packet analyzers (tcpdump, Wireshark) at network edges to identify if malformed SIP messages are reaching internal devices.
    Affected if Malformed SIP packets targeting affected devices are observed traversing the network.

Your environment is affected if you have devices using any of the listed Qualcomm chipsets (Agatti, Apq8053, Apq8096au, Apq8098, Bitra, Kamorta, Msm8905, Msm8909w) that have SIP/VoIP functionality enabled and are exposed to SIP network traffic.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied firmware patches from Qualcomm and device OEMs. As an interim control, implement network-level filtering of SIP traffic at perimeter firewalls to block malformed SIP messages before they reach affected devices.

Fix this in Agatti Firmware Scoped from the published advisory
  • Consultation16.0 h
  • Implementation24.0 h
  • Testing32.0 h
  • Review / QA12.0 h
84.0 hours of engineering $14,480
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $23,168.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-3654 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-3654 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data