A weekend-DIY buffer overflow in a discontinued closet access point
CVE-2026-15484 is a CWE-119 buffer overflow in the TRENDnet TEW-821DAP AC1200 Dual Band PoE Access Point, firmware 1.12B01 on hardware v1.xR. TRENDnet has previously acknowledged that TEW-821DAP firmware families carry buffer overflow and command injection issues in the web management interface reachable after authentication, which is consistent with the CVSS vector AV:N/AC:L/PR:L. Successful exploitation lands code execution on the AP's Linux userland, giving full pivot into whatever VLAN the management interface sits on.
The vendor HIGH (8.8) rating is defensible on paper — you get full C/I/A impact — but it substantially overstates the enterprise risk. The device is a legacy SOHO/small-business AP, not deployed in managed enterprise fleets at meaningful volume, and exploitation requires valid admin credentials on the web UI. In a hardened deployment (management VLAN + non-default creds + no WAN-side admin) the reachable population is a rounding error. Treat this as a MEDIUM in a managed environment; it stays HIGH only if you actually run these APs with default creds on a flat network.
5 steps from start to impact.
Reach the admin web interface
- Network path to management IP
- Management service listening (default: enabled)
- Management VLAN isolation
- ACLs restricting admin plane to jump host
- No WAN-side admin exposure by default
Authenticate to the web UI
PR:L confirms authentication is required. Attacker must supply valid low-privilege credentials — realistically the admin account, since TEW-821DAP does not implement meaningful role separation. Default credentials (admin/admin) remain a common path on unmanaged deployments.- Valid credentials
- OR default credentials still in place
- OR credential reuse from another compromise
- Non-default password (basic hardening)
- No SSO/LDAP means creds are typically unique per device
- Lockout after failed attempts on newer firmware
Send oversized request to vulnerable endpoint
goahead/httpd variants are typical for this class of device). Public PoCs for sibling TEW-821DAP CVEs (CVE-2026-7606..7611) demonstrate the same class of overflow using curl with long query strings. No custom tooling required.- Authenticated session cookie
- Knowledge of vulnerable endpoint (from PoC or fuzzing)
- No stack canaries / ASLR on this MIPS/ARM firmware means exploitation is easy once you've authenticated — friction here is LOW
Code execution as root on the AP
/etc/init.d, sniff client traffic, inject captive-portal payloads, or pivot into the management VLAN.- Working ROP chain / shellcode for MIPS/ARM target
- Firmware read-only overlay may complicate persistence but does not prevent runtime compromise
Pivot into corporate segments
- Reachable internal services from AP's VLAN
- 802.1X + strong segmentation limits pivot
- RADIUS on isolated network limits credential capture
- EDR / AV — the AP runs BusyBox/embedded Linux with no agent surface. Your EDR fleet is blind here.
- WPA2/WPA3 upgrade — this bug is in the HTTP admin interface, not the wireless auth stack. Changing PSKs does nothing.
- WAF rules on the corporate WAF — the AP admin UI is not behind your corporate WAF; blocking oversized params there doesn't help.
- MFA — the TEW-821DAP web UI does not support MFA. There's no lever to pull.
The supporting signals.
| In-the-wild exploitation | None observed. Not KEV-listed. No public campaigns tied to this specific CVE ID. |
|---|---|
| Public PoC | No PoC for CVE-2026-15484 specifically at time of writing; sibling TEW-821DAP overflow CVEs (CVE-2026-7606 through 7611) have public PoCs demonstrating the class. |
| EPSS | Not yet scored (disclosure 2026-07-12) — expect <1st percentile given legacy SOHO footprint. |
| KEV status | Not listed. |
| CVSS vector | AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H — network-reachable but requires authentication. |
| Affected versions | TEW-821DAP hardware v1.xR, firmware 1.12B01. v2.0R uses different firmware trees. |
| Fixed version | No fix expected — device is end-of-life per TRENDnet's support lifecycle. Vendor guidance is typically 'restrict management access'. |
| Exposure data | Shodan queries for TRENDnet admin banners return low-thousands globally, dominated by residential/small-business ISPs — negligible enterprise footprint. |
| Disclosure date | 2026-07-12 |
| Reporter | Not disclosed in available sources at time of assessment. |
Sources.
- TRENDnet TEW-821DAP product page
- TRENDnet TEW-821DAP firmware downloads
- TRENDnet customer support / advisories
- OpenCVE — TRENDnet CVE listings
- Feedly — Latest TRENDnet vulnerabilities
- TRENDnet CVE Vulnerabilities & Metrics (akaoma)
- TRENDnet threat intelligence index
- CWE-119: Improper Restriction of Operations within the Bounds of a Memory Buffer
Why this verdict
- Authentication gate (
PR:L): attacker must already possess admin credentials. This alone removes the mass-scanning threat model and pushes the CVE below its vendor-assigned 8.8. - Deployment role — low-value: the TEW-821DAP is a SOHO/small-business AP. It is not a domain controller, hypervisor, IdP, or backup server. Even root on the device caps blast radius at the local wireless segment plus whatever the management VLAN reaches.
- Role multiplier: in the WORST realistic role (flat-network SMB with default creds and no VLAN separation), the chain succeeds and yields root on AP + wireless sniff + local pivot. That's a real HIGH for THAT deployment — but this device class is <0.1% of managed enterprise AP installed base per Gartner/IDC wireless share reporting, so the floor does not raise for enterprise readers.
- No KEV, no observed exploitation, no confirmed PoC for this specific CVE ID at disclosure.
- Legacy hardware, no patch pipeline — this pushes toward *replacement* rather than *patch*, which is a MEDIUM-track workflow (asset retirement), not a CRITICAL-track workflow (emergency patch).
Why not higher?
HIGH would require either (a) unauthenticated reach, (b) active exploitation, or (c) a role multiplier where the affected device sits at identity/hypervisor/edge scale. None apply: authentication is required, no exploitation is observed, and the TEW-821DAP is a leaf access point.
Why not lower?
LOW would require the impact to be trivial or the exposure to be effectively zero. Neither is true — successful exploitation is root on a network device that bridges wireless and wired segments, and SOHO/legacy deployments where this AP still runs are precisely the ones with weak credential hygiene. MEDIUM correctly captures 'real risk for a narrow, poorly-managed installed base'.
Crowdsourced verification payload.
Run this from an auditor workstation on the management VLAN with reachability to the AP. Invoke as ./check-tew821dap.sh 10.0.0.5 where the argument is the AP's management IP. Requires only curl — no credentials, no privileges on the target.
#!/usr/bin/env bash
# noisgate check for CVE-2026-15484 (TRENDnet TEW-821DAP v1.12B01 buffer overflow)
# Fingerprints firmware version via the login/status pages.
# Exit codes: 0 PATCHED / not-affected model, 1 VULNERABLE, 2 UNKNOWN
set -u
if [[ $# -lt 1 ]]; then
echo "usage: $0 <ap-mgmt-ip> [port]" >&2
exit 2
fi
TARGET="$1"
PORT="${2:-80}"
URL="http://${TARGET}:${PORT}"
UA="noisgate-check/1.0"
BODY=$(curl -sS --max-time 5 -A "$UA" "${URL}/login.asp" "${URL}/status.asp" "${URL}/index.asp" 2>/dev/null || true)
if [[ -z "$BODY" ]]; then
echo "UNKNOWN: no HTTP response from ${TARGET}:${PORT}"
exit 2
fi
if ! echo "$BODY" | grep -qiE 'TEW-821DAP|TRENDnet'; then
echo "UNKNOWN: not a TEW-821DAP admin interface"
exit 2
fi
if echo "$BODY" | grep -qE '1\.12B01|v1\.12'; then
echo "VULNERABLE: ${TARGET} is TEW-821DAP firmware 1.12B01 (CVE-2026-15484)"
exit 1
fi
if echo "$BODY" | grep -qE 'v2\.[0-9]+'; then
echo "PATCHED: ${TARGET} is hardware v2 — not in affected range"
exit 0
fi
echo "UNKNOWN: TEW-821DAP detected but firmware string not parsed — inspect manually"
exit 2