CVE-2026-10121
Stack-Based Buffer Overflow in TRENDnet TEW-432BRP
Publication date: 2026-05-30
Last updated on: 2026-05-30
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| trendnet | tew-432brp | 3.10b20 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-119 | The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data. |
| CWE-121 | A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function). |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a stack-based buffer overflow found in the TRENDnet TEW-432BRP router, specifically in the function formSetUrlFilter located at /goform/formSetUrlFilter.
The issue arises because user input from the keyword_list parameter is copied directly into a local stack variable without proper validation, allowing an attacker to overwrite the function's return address.
By sending a long string (for example, 200 or more 'a' characters) in a POST request to this endpoint, an attacker can cause the router to crash and become unresponsive.
This vulnerability can be exploited remotely and a proof-of-concept exploit has been published.
How can this vulnerability impact me? :
Exploiting this vulnerability can cause the affected router to crash and become unresponsive, leading to a denial of service.
This disruption can interrupt network services relying on the router, potentially affecting connectivity and availability.
Since the device is no longer supported by the vendor, no official fixes are available, increasing the risk of prolonged exposure.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by sending a specially crafted POST request to the endpoint /goform/formSetUrlFilter with a long string (e.g., 200 or more 'a' characters) in the keyword_list parameter. If the device crashes or becomes unresponsive after this request, it indicates the presence of the vulnerability.
An example command using curl to test this would be:
- curl -X POST http://[router_ip]/goform/formSetUrlFilter -d "keyword_list=$(python3 -c 'print("a"*200)')"
If the router crashes or stops responding after this command, it confirms the vulnerability.
What immediate steps should I take to mitigate this vulnerability?
Since the affected TRENDnet TEW-432BRP device has been end-of-life for 15 years and the vendor does not provide fixes, immediate mitigation steps include:
- Discontinue use of the vulnerable device and replace it with a supported, updated router model.
- If replacement is not immediately possible, restrict remote access to the device to trusted networks only, preventing exposure to untrusted sources.
- Monitor network traffic for suspicious POST requests to /goform/formSetUrlFilter with unusually long keyword_list parameters and block such traffic if possible.
No official patch or fix is available due to the product's age and end-of-life status.