Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessSend HTTP POST request to /ping_response.cgi
-
ExploitInject oversized ping_ipaddr parameter
-
ExecutionOverflow stack buffer
-
ImpactExecute arbitrary code on router
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2021 - Vulnerable and Outdated Components
ASVS 5.0
V15 - Secure Coding and Architecture Stack buffer bounds checking
MITRE ATT&CK
1 technique across 1 tactic: Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | TRENDnet TEW-632BRP firmware version 1.010B32 with HTTP POST request handler enabled. Requires authenticated access with high privileges (PR:H). Remote attacker must have administrative credentials or access to management interface. |
| Impact | Despite the high CVSS score of 7.2, the real-world risk is moderated by several factors. The CVSS vector (AV:N/AC:L/PR:H/UI:N/S:U) indicates remote exploitation is possible but requires high privileges, suggesting authentication is needed. The exploitation code maturity is 'Proof-of-Concept' (E:P) with a remediation level of 'X' (undefined). While a public POC exists on GitHub, the lack of CISA KEV listing suggests no known active exploitation in the wild. No EPSS score is available to assess exploitation likelihood. The vendor's non-response to disclosure is concerning, indicating no patch is available. This presents moderate risk for organizations using affected devices, especially if administrative credentials are weak or compromised. |
| Exploit ScenarioDerived | An attacker who has obtained valid administrative credentials (through phishing, credential stuffing, or default passwords) can remotely access the router's web interface and send a specially crafted HTTP POST request to /ping_response.cgi. By providing an oversized value in the ping_ipaddr parameter, the attacker triggers a stack buffer overflow, potentially gaining code execution on the device. The public POC available at https://github.com/i-Corner/cve/issues/40 demonstrates this attack. Given the low attack complexity (AC:L) and network attack vector (AV:N), exploitation is straightforward once authentication is bypassed. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Mar 15, 2026
Stack-based buffer overflow vulnerability in TRENDnet TEW-632BRP firmware version 1.010B32, specifically in the ping_response.cgi file's HTTP POST request handler. An authenticated attacker with high privileges can exploit this vulnerability remotely to achieve code execution with high impact to confidentiality, integrity, and availability. A public proof-of-concept exploit is available on GitHub, though the vulnerability is not listed in CISA KEV and no EPSS score is provided.
RemediationAI
No official patch or firmware update is available as the vendor did not respond to the vulnerability disclosure. Recommended mitigations include: 1) Replace affected TEW-632BRP devices with newer, supported models; 2) Restrict administrative access to trusted IP addresses only; 3) Use strong, unique administrative credentials; 4) Disable remote administration if not required; 5) Place the device behind a properly configured firewall to limit exposure. Monitor VulDB (ID: 351079) for any future vendor response or patch availability.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability affects TRENDnet's TEW-632BRP wireless router (CPE: cpe:2.3:a:trendnet:tew-632brp:*:*:*:*:*:*:*:*) running firmware version 1.010B32. The root cause is CWE-121 (Stack-based Buffer Overflow), where the ping_ipaddr parameter in /ping_response.cgi is not properly validated before being copied to a fixed-size stack buffer. This is a classic memory corruption issue in embedded device web interfaces, where user-supplied input to diagnostic utilities (ping functionality) is not sanitized, allowing an attacker to overwrite the stack and potentially execute arbitrary code.
Know when Tew 632brp gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
Lifecycle Timeline
3DescriptionCVE.org
A vulnerability was detected in TRENDnet TEW-632BRP 1.010B32. This affects an unknown part of the file /ping_response.cgi of the component HTTP POST Request Handler. The manipulation of the argument ping_ipaddr results in stack-based buffer overflow. The attack may be performed from remote. The exploit is now public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
Executive ViewAI
A publicly exploitable remote code execution vulnerability affects TRENDnet TEW-632BRP routers with no available patch from the vendor. Organizations using this device model face immediate risk of unauthorized access, data theft, and network compromise, particularly concerning for businesses relying on this equipment for network perimeter security.
Implement Web Application Firewall (WAF) rules to block POST requests to /ping_response.cgi with suspicious ping_ipaddr parameters; disable HTTP/HTTPS management interfaces and restrict administrative access to trusted IP ranges only; segment affected routers behind additional network boundaries; disable ICMP ping functionality if operationally feasible; monitor firewall logs for exploitation attempts; consider implementing network intrusion detection signatures for this CVE.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
A stack-based buffer overflow occurs when a program writes more data to a buffer located on the stack than it was allocated to hold.
EUVD-2026-12218
NVD
CVE.org
EPSS
GitHub
VulDB
Exploit-DB