CVE-2023-33017
📋 TL;DR
This CVE describes a memory corruption vulnerability in the UEFI boot process when running a ListVars test during boot. It affects Qualcomm devices with vulnerable firmware, potentially allowing attackers to execute arbitrary code during early boot stages before operating system security controls are active.
💻 Affected Systems
- Qualcomm chipsets with vulnerable UEFI firmware
📦 What is this software?
Flight Rb5 5g Platform Firmware by Qualcomm
Snapdragon 1100 Wearable Platform Firmware by Qualcomm
View all CVEs affecting Snapdragon 1100 Wearable Platform Firmware →
Snapdragon 1200 Wearable Platform Firmware by Qualcomm
View all CVEs affecting Snapdragon 1200 Wearable Platform Firmware →
Snapdragon 208 Processor Firmware by Qualcomm
Snapdragon 210 Processor Firmware by Qualcomm
Snapdragon 212 Mobile Platform Firmware by Qualcomm
View all CVEs affecting Snapdragon 212 Mobile Platform Firmware →
Snapdragon 4 Gen 2 Mobile Platform Firmware by Qualcomm
View all CVEs affecting Snapdragon 4 Gen 2 Mobile Platform Firmware →
Snapdragon 662 Mobile Platform Firmware by Qualcomm
View all CVEs affecting Snapdragon 662 Mobile Platform Firmware →
Snapdragon 675 Mobile Platform Firmware by Qualcomm
View all CVEs affecting Snapdragon 675 Mobile Platform Firmware →
Snapdragon 7c\+ Gen 3 Compute Firmware by Qualcomm
View all CVEs affecting Snapdragon 7c\+ Gen 3 Compute Firmware →
Snapdragon 8 Gen 2 Mobile Platform Firmware by Qualcomm
View all CVEs affecting Snapdragon 8 Gen 2 Mobile Platform Firmware →
Snapdragon 8 Gen 2 Mobile Platform Firmware by Qualcomm
View all CVEs affecting Snapdragon 8 Gen 2 Mobile Platform Firmware →
Snapdragon 835 Mobile Pc Platform Firmware by Qualcomm
View all CVEs affecting Snapdragon 835 Mobile Pc Platform Firmware →
Snapdragon 845 Mobile Platform Firmware by Qualcomm
View all CVEs affecting Snapdragon 845 Mobile Platform Firmware →
Snapdragon Ar2 Gen 1 Platform Firmware by Qualcomm
View all CVEs affecting Snapdragon Ar2 Gen 1 Platform Firmware →
Snapdragon Auto 4g Modem Firmware by Qualcomm
Snapdragon Auto 5g Modem Rf Firmware by Qualcomm
View all CVEs affecting Snapdragon Auto 5g Modem Rf Firmware →
Snapdragon Auto 5g Modem Rf Gen 2 Firmware by Qualcomm
View all CVEs affecting Snapdragon Auto 5g Modem Rf Gen 2 Firmware →
Snapdragon W5\+ Gen 1 Wearable Platform Firmware by Qualcomm
View all CVEs affecting Snapdragon W5\+ Gen 1 Wearable Platform Firmware →
Snapdragon Wear 1300 Platform Firmware by Qualcomm
View all CVEs affecting Snapdragon Wear 1300 Platform Firmware →
Snapdragon X12 Lte Modem Firmware by Qualcomm
Snapdragon X24 Lte Modem Firmware by Qualcomm
Snapdragon X5 Lte Modem Firmware by Qualcomm
Snapdragon X50 5g Modem Rf System Firmware by Qualcomm
View all CVEs affecting Snapdragon X50 5g Modem Rf System Firmware →
Snapdragon X55 5g Modem Rf System Firmware by Qualcomm
View all CVEs affecting Snapdragon X55 5g Modem Rf System Firmware →
Snapdragon X65 5g Modem Rf System Firmware by Qualcomm
View all CVEs affecting Snapdragon X65 5g Modem Rf System Firmware →
Snapdragon X75 5g Modem Rf System Firmware by Qualcomm
View all CVEs affecting Snapdragon X75 5g Modem Rf System Firmware →
Snapdragon Xr1 Platform Firmware by Qualcomm
Snapdragon Xr2 5g Platform Firmware by Qualcomm
View all CVEs affecting Snapdragon Xr2 5g Platform Firmware →
Snapdragon Xr2\+ Gen 1 Platform Firmware by Qualcomm
View all CVEs affecting Snapdragon Xr2\+ Gen 1 Platform Firmware →
Video Collaboration Vc1 Platform Firmware by Qualcomm
View all CVEs affecting Video Collaboration Vc1 Platform Firmware →
Video Collaboration Vc3 Platform Firmware by Qualcomm
View all CVEs affecting Video Collaboration Vc3 Platform Firmware →
Video Collaboration Vc5 Platform Firmware by Qualcomm
View all CVEs affecting Video Collaboration Vc5 Platform Firmware →
Vision Intelligence 300 Platform Firmware by Qualcomm
View all CVEs affecting Vision Intelligence 300 Platform Firmware →
⚠️ Risk & Real-World Impact
Worst Case
Complete system compromise via arbitrary code execution during boot, potentially allowing persistent firmware-level malware installation that survives OS reinstallation.
Likely Case
System crash or instability during boot, potentially leading to denial of service or limited code execution depending on exploit sophistication.
If Mitigated
No impact if patched firmware is installed or if physical access controls prevent unauthorized boot manipulation.
🎯 Exploit Status
Exploitation requires physical access or ability to manipulate boot process. Memory corruption during UEFI boot is complex to weaponize reliably.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: Check device manufacturer firmware updates
Vendor Advisory: https://www.qualcomm.com/company/product-security/bulletins/december-2023-bulletin
Restart Required: Yes
Instructions:
1. Check with device manufacturer for firmware updates. 2. Apply firmware update following manufacturer instructions. 3. Reboot device to activate patched firmware.
🔧 Temporary Workarounds
Secure Boot Enforcement
allEnable and enforce Secure Boot to prevent unauthorized boot modifications
Physical Security Controls
allImplement physical security measures to prevent unauthorized device access during boot
🧯 If You Can't Patch
- Implement strict physical access controls to prevent unauthorized boot manipulation
- Use device encryption and secure boot features to limit impact of potential exploitation
🔍 How to Verify
Check if Vulnerable:
Check device firmware version against manufacturer's patched versions. Use manufacturer-specific tools to verify UEFI firmware version.
Check Version:
Manufacturer-specific commands vary; consult device documentation for firmware version checking.
Verify Fix Applied:
Verify firmware version has been updated to patched version. Test boot process stability with ListVars functionality if available.
📡 Detection & Monitoring
Log Indicators:
- Unexpected boot failures
- UEFI firmware error messages
- System instability during boot phase
Network Indicators:
- None - this is a local boot-time vulnerability
SIEM Query:
Search for: 'boot failure', 'UEFI error', 'firmware crash' in system logs during boot events