{"id":"CVE-2020-3704","url":"https://www.cyber-defence.io/tools/cve/CVE-2020-3704","generatedAt":"2026-10-28T05:26:31.187Z","title":"u'While processing invalid connection request PDU which is nonstandard (interval or timeout is 0) from central device may lead peripheral system enter into dead lock state.(This CVE is equivalent to InvalidConnectionRequest(CVE-2019-19193) mentioned in…","description":"u'While processing invalid connection request PDU which is nonstandard (interval or timeout is 0) from central device may lead peripheral system enter into dead lock state.(This CVE is equivalent to InvalidConnectionRequest(CVE-2019-19193) mentioned in sweyntooth paper)' in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking in Agatti, APQ8009, APQ8017, APQ8053, AR9344, Bitra, IPQ5018, Kamorta, MDM9607, MDM9640, MDM9650, MSM8996AU, Nicobar, QCA6174A, QCA6390, QCA6574AU, QCA9377, QCA9886, QCM6125, QCN7605, QCS404, QCS405, QCS605, QCS610, QRB5165, Rennell, SA415M, SA515M, Saipan, SC7180, SC8180X, SDA845, SDM660, SDM670, SDM710, SDM845, SDM850, SDX20, SDX24, SDX55, SM6150, SM7150, SM8150, SM8250, SXR1130, SXR2130","published":"2020-11-02T07:15:15.000Z","lastModified":"2026-06-17T03:18:54.000Z","status":"Modified","sourceIdentifier":"product-security@qualcomm.com","cvss":{"version":"3.1","score":7.5,"severity":"HIGH","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H"},"cwe":["CWE-667"],"affected":["qualcomm/agatti firmware","qualcomm/apq8009 firmware","qualcomm/apq8017 firmware","qualcomm/apq8053 firmware","qualcomm/ar9344 firmware","qualcomm/bitra firmware","qualcomm/ipq5018 firmware","qualcomm/kamorta firmware","qualcomm/mdm9607 firmware","qualcomm/mdm9640 firmware","qualcomm/mdm9650 firmware","qualcomm/msm8996au firmware","qualcomm/nicobar firmware","qualcomm/qca6174a firmware","qualcomm/qca6390 firmware","qualcomm/qca6574au firmware","qualcomm/qca9377 firmware","qualcomm/qca9886 firmware","qualcomm/qcm6125 firmware","qualcomm/qcn7605 firmware","qualcomm/qcs404 firmware","qualcomm/qcs405 firmware","qualcomm/qcs605 firmware","qualcomm/qcs610 firmware","qualcomm/qrb5165 firmware","qualcomm/rennell firmware","qualcomm/sa415m firmware","qualcomm/sa515m firmware","qualcomm/saipan firmware","qualcomm/sc7180 firmware","qualcomm/sc8180x firmware","qualcomm/sda845 firmware","qualcomm/sdm660 firmware","qualcomm/sdm670 firmware","qualcomm/sdm710 firmware","qualcomm/sdm845 firmware","qualcomm/sdm850 firmware","qualcomm/sdx20 firmware","qualcomm/sdx24 firmware","qualcomm/sdx55 firmware","qualcomm/sm6150 firmware","qualcomm/sm7150 firmware","qualcomm/sm8150 firmware","qualcomm/sm8250 firmware","qualcomm/sxr1130 firmware","qualcomm/sxr2130 firmware"],"epss":{"score":0.00532,"percentile":0.44732,"date":"2026-10-27","history":[]},"kev":{"listed":false},"exploits":{"count":0,"verified":false,"firstPublished":null,"source":"Exploit-DB (https://gitlab.com/exploit-database/exploitdb)","entries":[]},"verdict":{"level":"high","text":"High impact if exploited, but EPSS currently rates exploitation as unlikely (0.53%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit."},"changes":[],"references":[{"url":"https://www.qualcomm.com/company/product-security/bulletins/october-2020-bulletin","tags":["Broken Link"],"source":"product-security@qualcomm.com"},{"url":"https://www.qualcomm.com/company/product-security/bulletins/october-2020-security-bulletin","tags":["Vendor Advisory"],"source":"nvd@nist.gov"},{"url":"https://www.qualcomm.com/company/product-security/bulletins/october-2020-bulletin","tags":["Broken Link"],"source":"af854a3a-2127-422b-91ae-364da2661108"}],"sources":{"nvd":"https://nvd.nist.gov/vuln/detail/CVE-2020-3704","epss":"https://www.first.org/epss/","kev":"https://www.cisa.gov/known-exploited-vulnerabilities-catalog","exploitdb":"https://www.exploit-db.com/"},"licence":"CC BY 4.0 — link back to the CVE Explorer if you publish the results; upstream data remains subject to its own terms."}