CVE-2025-12211
BaseFortify
Publication date: 2025-10-27
Last updated on: 2026-02-24
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| tenda | o3_firmware1.0.0.10\(2478\) | * |
| tenda | o3 | 2.0 |
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 O3 1.0.0.10(2478) device, specifically in the SetValue/GetValue functions of the /goform/setDmzInfo file. It occurs due to improper handling of the dmzIP argument, allowing an attacker to remotely exploit the overflow and potentially execute arbitrary code or cause a denial of service. [1]
How can this vulnerability impact me? :
Exploitation of this vulnerability can allow a remote attacker to execute arbitrary code, disrupt device functionality, or cause a denial of service. This can lead to unauthorized control over the affected device, potentially compromising network security and availability. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection can involve monitoring network traffic for requests to the /goform/setDmzInfo endpoint with suspicious or malformed dmzIP parameters that could trigger the stack-based buffer overflow. Specific commands are not provided in the resources, but using tools like curl or wget to send crafted requests to the vulnerable endpoint or employing network intrusion detection systems (NIDS) with signatures targeting this exploit could help detect attempts. For example, a curl command to test might be: curl -X POST http://<target-ip>/goform/setDmzInfo -d 'dmzIP=<malicious_payload>'. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting remote access to the affected device, especially blocking access to the /goform/setDmzInfo endpoint from untrusted networks. Applying any available firmware updates or patches from the vendor is critical. If no patch is available, disabling the DMZ feature or the vulnerable service temporarily can reduce risk. Additionally, monitoring for exploit attempts and employing network-level protections such as firewalls or intrusion prevention systems can help mitigate exploitation. [1]