CVE-2020-3615: Critical severity android vulnerability
Valid deauth/disassoc frames is dropped in case if RMF is enabled and some rouge peer keep on sending rogue deauth/disassoc frames due to improper enum values used to check the frame subtype in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile in APQ8009, APQ8053, APQ8096AU, MDM9150, MDM9206, MDM9207C, MDM9607, MDM9650, MSM8996AU, QCA6174A, QCA6574AU, QCA9377, QCA9379, QCN7605, QCS605, SC8180X, SDM630, SDM636, SDM660, SDM845, SDX20, SDX24, SDX55, SM8150, SXR1130
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2020-3615?
The severity of CVE-2020-3615 is considered critical, as it can allow rogue devices to disrupt connectivity by sending deauthentication frames.
How do I fix CVE-2020-3615?
To address CVE-2020-3615, ensure that you apply the latest firmware updates from Qualcomm that correct the handling of deauth/disassoc frames.
What systems are affected by CVE-2020-3615?
CVE-2020-3615 affects multiple Qualcomm Snapdragon platforms, including various firmware and system on chip (SoC) products.
Can CVE-2020-3615 be exploited remotely?
Yes, CVE-2020-3615 can be exploited remotely by an attacker within range of the affected wireless network.
Is CVE-2020-3615 related to wireless security?
Yes, CVE-2020-3615 specifically pertains to vulnerabilities in wireless network protocols and the handling of deauthentication frames.