CVE-2025-15178
Stack-Based Buffer Overflow in Tenda WH450 HTTP Handler
Publication date: 2025-12-29
Last updated on: 2025-12-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| tenda | wh450 | 1.0.0.18 |
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 in the Tenda WH450 router's HTTP Request Handler component, specifically in the processing of the /goform/VirtualSer file. It occurs due to improper handling of the 'page' argument, allowing an attacker to remotely exploit the issue by sending crafted requests.
How can this vulnerability impact me? :
The vulnerability can lead to severe impacts including complete compromise of the affected device. Since it allows remote exploitation, an attacker could execute arbitrary code, potentially gaining control over the router, leading to data breaches, service disruption, or further attacks on the network.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring HTTP requests to the /goform/VirtualSer endpoint for unusually long or malformed 'page' parameter values that may indicate an exploit attempt. Network intrusion detection systems (NIDS) or web application firewalls (WAF) can be configured to alert on such suspicious requests. Specific commands are not provided in the resources, but using tools like curl or wget to send crafted requests to /goform/VirtualSer and observing the device's response may help detect the vulnerability. Additionally, reviewing logs for repeated or abnormal requests to this endpoint can assist in detection. [1, 3]
What immediate steps should I take to mitigate this vulnerability?
No known countermeasures or mitigations currently exist for this vulnerability. It is suggested to replace the affected product with an alternative device to mitigate the risk. Until a patch or fix is available, restricting access to the device's management interface and monitoring for exploit attempts are recommended as temporary measures. [3]