dbcve.org
Agatti FirmwareOperating system · Qualcomm

CVE-2020-3673

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 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

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

Buffer overflow vulnerability in SIP message packet processing within Qualcomm Snapdragon chipsets. The vulnerability exists due to lack of bounds checking when storing values in an array during SIP message handling, allowing an attacker to overflow the buffer by providing an index exceeding the allocated array length.

MitigationApply vendor-provided firmware/security patches from Qualcomm to affected chipsets. Until patches are available, consider network-level filtering of SIP traffic and disable SIP services if not essential.

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 your device chipset model
    Check the device specifications, hardware documentation, or system information to determine the Qualcomm Snapdragon chipset in use (e.g., Agatti, Apq8053, Apq8096au, Apq8098, Bitra, Kamorta, Msm8905, Msm8909w)
    Affected if The chipset matches one of the affected models listed in the CVE (Agatti, Apq8053, Apq8096au, Apq8098, Bitra, Kamorta, Msm8905, Msm8909w)
  2. Determine the firmware version
    Check the device firmware or baseband version information typically found in device settings under 'About Phone', 'Baseband', or via AT commands on modem interfaces
    Affected if The device is running firmware on any of the affected chipset models (all versions of the listed firmware are affected)
  3. Check if SIP service is enabled
    Inspect the device or network configuration for SIP (Session Initiation Protocol) service settings. This may be in VoIP settings, telephony configuration, or network service settings
    Affected if SIP service or VoIP functionality is enabled on the device
  4. Verify SIP traffic exposure
    Monitor network traffic or check firewall rules to determine if the device is exposing SIP ports (typically port 5060) to untrusted networks or processing SIP messages from external sources
    Affected if The device processes SIP traffic from network sources, particularly untrusted or external sources

You are likely affected if your device uses one of the listed Qualcomm chipsets (Agatti, Apq8053, Apq8096au, Apq8098, Bitra, Kamorta, Msm8905, Msm8909w) and has SIP service enabled or processes SIP 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-provided firmware/security patches from Qualcomm to affected chipsets. Until patches are available, consider network-level filtering of SIP traffic and disable SIP services if not essential.

Fix this in Agatti Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-3673 — 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-3673 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