CVE-2021-35395: Realtek AP-Router SDK Buffer Overflow
Realtek AP-Router SDK · listed in the CISA catalog of actively exploited vulnerabilities since 2021-11-03.
- CVSS v3.1 (CISA ADP)
- 9.8
- critical
- EPSS (exploit probability, 30 days)
- 98%
- among the highest 0.1% of all CVEs
- Added to CISA KEV
- 2021-11-03
- US federal due date 2021-11-17
- Automatable (CISA SSVC)
- yes
- technical impact: total
CVE-2021-35395 explained
CVE-2021-35395 covers several flaws in the HTTP management web server of the Realtek AP-Router SDK (Jungle SDK), used by many device makers in access points and routers. Stack buffer overflows and command injection in the webs and boa binaries let remote attackers run arbitrary code on the device. CISA lists it as known to be exploited.
Impact
A remote attacker who can reach the management interface over the network can gain arbitrary code execution on the device. No privileges or user interaction are required, and attack complexity is low. CISA rates it automatable with total technical impact, meaning attackers can exploit it at scale and take full control. Exploitability varies by how each manufacturer adapted the SDK web server, for example whether they added authentication or removed features.
Who is affected
The CVE record lists Realtek AP-Router SDK but names no specific affected versions and no fixed version. The description says Realtek Jungle SDK version v2.x up to v3.4.14B is affected, in both the Go-Ahead based webs and the Boa based boa management servers. Devices from other manufacturers built on this SDK may be affected, and their custom code may contain additional similar issues.
Written with AI from the data on this page and checked against it automatically.
Official description
Realtek Jungle SDK version v2.x up to v3.4.14B provides an HTTP web server exposing a management interface that can be used to configure the access point. Two versions of this management interface exists: one based on Go-Ahead named webs and another based on Boa named boa.
Both of them are affected by these vulnerabilities. Specifically, these binaries are vulnerable to the following issues: - stack buffer overflow in formRebootCheck due to unsafe copy of submit-url parameter - stack buffer overflow in formWsc due to unsafe copy of submit-url parameter - stack buffer overflow in formWlanMultipleAP due to unsafe copy of submit-url parameter - stack buffer overflow in formWlSiteSurvey due to unsafe copy of ifname parameter - stack buffer overflow in formStaticDHCP due to unsafe copy of hostname parameter - stack buffer overflow in formWsc due to unsafe copy of 'peerPin' parameter - arbitrary command execution in formSysCmd via the sysCmd parameter - arbitrary command injection in formWsc via the 'peerPin' parameter Exploitability of identified issues will differ based on what the end vendor/manufacturer did with the Realtek SDK webserver.
Some vendors use it as-is, others add their own authentication implementation, some kept all the features from the server, some remove some of them, some inserted their own set of features. However, given that Realtek SDK implementation is full of insecure calls and that developers tends to re-use those examples in their custom code, any binary based on Realtek SDK webserver will probably contains its own set of issues on top of the Realtek ones (if kept).
Successful exploitation of these issues allows remote attackers to gain arbitrary code execution on the device.
CISA required action: Apply updates per vendor instructions.
CISA notes
How to fix it
- The CVE record names no fixed version – check the vendor advisory and CISA's required action for updates and mitigations.
- Vendor advisory: realtek.com/en/cu-1-en/cu-1-taiwan-en
- CISA's deadline for US federal agencies: 2021-11-17 (passed) – a useful benchmark for everyone else, too.
What to do
- Identify routers, access points and IoT devices built on the Realtek SDK web server, using manufacturer information.
- Apply firmware updates per the device manufacturer's and vendor's instructions, as CISA's required action states.
- Keep device management interfaces off the internet and restrict access to trusted management networks.
- Check exposed devices for signs of compromise, such as unexpected configuration changes or unknown processes.
- Replace devices for which the manufacturer provides no updated firmware.
The CVE record names no fixed version. Follow the vendor advisory and CISA's required action to apply updates per vendor instructions, and check your device manufacturer for firmware based on a corrected SDK. Until updated firmware is installed, block internet access to the management interface, limit it to trusted hosts, and monitor devices for signs of compromise.
Written with AI from the data on this page and checked against it automatically.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- Yes – attackers can automate it at scale
- Technical impact
- Total – full control of the component or total information disclosure
Questions about CVE-2021-35395
- Is CVE-2021-35395 being exploited?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2021-11-03, with a US federal due date of 2021-11-17. Known ransomware use is listed as unknown.
- Why is it hard to know if my device is affected?
- The flaws are in the Realtek SDK web server, which manufacturers reuse and modify. Some add authentication or remove features, which changes exploitability. Check with your device manufacturer whether your firmware uses the affected SDK.
- Which fixed version should I install?
- The CVE record names no fixed version. Follow the vendor advisory and your device manufacturer's firmware updates, as CISA's required action directs.
Written with AI from the data on this page and checked against it automatically.
References
Vendor
Trackers and catalogs
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-22. Always confirm with the vendor's or distribution's advisory before patching.