CVE-2025-15180
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 exists in the Tenda WH450 device, specifically in an unknown function within the /goform/webExcptypemanFilte file of the HTTP Request Handler component. It involves manipulation of the 'page' argument, which leads to a stack-based buffer overflow. This type of vulnerability can be exploited remotely, and an exploit is publicly available.
How can this vulnerability impact me? :
The vulnerability can lead to a stack-based buffer overflow, which may allow an attacker to execute arbitrary code, cause a denial of service, or compromise the affected device remotely. Given the high CVSS scores, the impact includes potential full confidentiality, integrity, and availability loss of the device.
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 endpoint /goform/webExcptypemanFilte for unusually long or malformed 'page' parameter values that could trigger a stack-based buffer overflow. Network intrusion detection systems (NIDS) can be configured to alert on such suspicious HTTP requests. Additionally, manual inspection or automated scanning tools can send crafted HTTP requests with long 'page' parameters to test for vulnerability. Specific commands might include using curl or wget to send HTTP requests with long 'page' parameters, for example: curl -X POST 'http://<target-ip>/goform/webExcptypemanFilte' -d 'page=AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA...' to observe the device's response or crash behavior. [1, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting access to the affected device's HTTP interface, especially from untrusted networks, to prevent remote exploitation. Since no known countermeasures or patches are available, it is recommended to replace the affected product or upgrade to a non-vulnerable version if available. Monitoring network traffic for exploit attempts and applying network-level protections such as firewalls or intrusion prevention systems to block malicious requests targeting /goform/webExcptypemanFilte can also help reduce risk. [2]