CVE-2021-28840
📋 TL;DR
A null pointer dereference vulnerability in D-Link DAP series access points allows remote attackers to crash the httpd service via a specially crafted HTTP GET request. This affects multiple D-Link DAP models running specific vulnerable firmware versions. The vulnerability can cause denial of service, potentially disrupting network connectivity.
💻 Affected Systems
- D-Link DAP-2310
- D-Link DAP-2330
- D-Link DAP-2360
- D-Link DAP-2553
- D-Link DAP-2660
- D-Link DAP-2690
- D-Link DAP-2695
- D-Link DAP-3320
- D-Link DAP-3662
📦 What is this software?
⚠️ Risk & Real-World Impact
Worst Case
Complete denial of service causing the access point to crash and become unavailable, requiring physical restart and disrupting all connected devices.
Likely Case
HTTP service crash leading to temporary loss of web management interface and potential network instability until service restarts.
If Mitigated
Minimal impact with proper network segmentation and monitoring allowing quick detection and recovery.
🎯 Exploit Status
Exploitation requires sending a specific HTTP GET request to trigger the null pointer dereference. Public research papers detail the vulnerability mechanism.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: Check D-Link security bulletin for latest patched firmware versions
Vendor Advisory: https://www.dlink.com/en/security-bulletin/
Restart Required: Yes
Instructions:
1. Visit D-Link support website. 2. Download latest firmware for your specific DAP model. 3. Log into device web interface. 4. Navigate to firmware update section. 5. Upload and apply new firmware. 6. Reboot device after update completes.
🔧 Temporary Workarounds
Disable HTTP Management Interface
allDisable web management interface or restrict access to trusted networks only
Configure firewall rules to block external access to port 80/443 on DAP devices
Use CLI to disable httpd service if supported
Network Segmentation
allIsolate DAP devices on separate VLAN without internet exposure
Configure switch ports to place DAP on management VLAN
Set up ACLs to restrict access to DAP management IPs
🧯 If You Can't Patch
- Implement strict network access controls to limit HTTP access to DAP management interfaces
- Deploy network monitoring and IDS/IPS to detect and block exploitation attempts
🔍 How to Verify
Check if Vulnerable:
Check firmware version via web interface (System > Firmware) or CLI, compare against vulnerable versions listed in affected_systems.versions
Check Version:
Web interface: System > Firmware page; CLI: 'show version' or similar model-specific command
Verify Fix Applied:
Verify firmware version has been updated to a version not listed in affected_systems.versions, test HTTP service stability with normal management requests
📡 Detection & Monitoring
Log Indicators:
- HTTP service crash logs
- Repeated httpd process restarts
- Unusual HTTP GET requests to upload_config endpoints
Network Indicators:
- HTTP requests causing device unresponsiveness
- Increased HTTP error responses from DAP devices
SIEM Query:
source="dlink-dap" AND (http_request="*upload_config*" OR process="httpd" AND event="crash")
🔗 References
- https://github.com/zyw-200/EQUAFL/blob/main/dlink-email-cve.pdf
- https://github.com/zyw-200/EQUAFL/blob/main/dlink-email-cve2.pdf
- https://www.dlink.com/en/security-bulletin/
- https://github.com/zyw-200/EQUAFL/blob/main/dlink-email-cve.pdf
- https://github.com/zyw-200/EQUAFL/blob/main/dlink-email-cve2.pdf
- https://www.dlink.com/en/security-bulletin/