CVE-2026-7019
Remote Buffer Overflow in Tenda F456 fromP2pListFilter Function
Publication date: 2026-04-26
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| tenda | f456_firmware | 1.0.0.5 |
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-120 | The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-7019 is a stack-based buffer overflow vulnerability in the Tenda F456 router version 1.0.0.5. It exists in the function fromP2pListFilter within the HTTP daemon, specifically in the handling of a user-supplied parameter named "page". This parameter is copied into a buffer using the sprintf function without proper bounds checking, which allows an attacker to overflow the stack buffer.
An attacker can exploit this vulnerability remotely by sending a specially crafted HTTP POST request to the /goform/P2pListFilter endpoint with an excessively long "page" parameter, causing the buffer overflow.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring for suspicious HTTP POST requests sent to the endpoint /goform/P2pListFilter with an unusually long or crafted "page" parameter. Such requests may indicate attempts to exploit the stack-based buffer overflow.
A detection method involves capturing and inspecting HTTP traffic to the Tenda F456 router, specifically looking for POST requests targeting /goform/P2pListFilter.
Example command using curl to test the vulnerability by sending a crafted request (for detection or testing purposes):
- curl -X POST http://[router_ip]/goform/P2pListFilter -d "page=$(python3 -c 'print("A"*1000)')"
Network administrators can also use packet capture tools like tcpdump or Wireshark to filter and analyze HTTP POST requests to /goform/P2pListFilter for abnormal payload sizes.
- tcpdump -i [interface] -A 'tcp port 80 and (((ip[2:2] - ((ip[0]&0xf)<<2)) - ((tcp[12]&0xf0)>>2)) != 0)' | grep '/goform/P2pListFilter'
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting access to the vulnerable endpoint /goform/P2pListFilter by implementing firewall rules or access control lists to block unauthorized or external HTTP POST requests to this path.
If possible, disable remote management or HTTP access to the router from untrusted networks to reduce exposure.
Monitor the device for unusual behavior or crashes that may indicate exploitation attempts.
Apply any available firmware updates or patches from the vendor that address this vulnerability once released.
How can this vulnerability impact me? :
Exploiting this vulnerability can lead to a denial of service (DoS) on the affected device or potentially allow an attacker to execute arbitrary remote code. This means an attacker could crash the router or take control of it remotely, leading to disruption of network services or unauthorized access.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided information does not specify any direct impact of this vulnerability on compliance with common standards and regulations such as GDPR or HIPAA.