Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-12211: Stack-based Buffer Overflow in Tenda O3

0
High
VulnerabilityCVE-2025-12211cvecve-2025-12211
Published: Mon Oct 27 2025 (10/27/2025, 03:32:06 UTC)
Source: CVE Database V5
Vendor/Project: Tenda
Product: O3

Description

A security flaw has been discovered in Tenda O3 1.0.0.10(2478). Affected by this issue is the function SetValue/GetValue of the file /goform/setDmzInfo. The manipulation of the argument dmzIP results in stack-based buffer overflow. It is possible to launch the attack remotely. The exploit has been released to the public and may be exploited.

AI-Powered Analysis

AILast updated: 11/03/2025, 06:06:59 UTC

Technical Analysis

CVE-2025-12211 is a stack-based buffer overflow vulnerability identified in Tenda O3 firmware version 1.0.0.10(2478). The vulnerability resides in the /goform/setDmzInfo endpoint, specifically within the SetValue and GetValue functions that handle the dmzIP parameter. Improper validation or sanitization of this input allows an attacker to overflow the stack buffer, leading to memory corruption. This flaw can be triggered remotely over the network without requiring authentication or user interaction, making it highly exploitable. Successful exploitation could enable an attacker to execute arbitrary code on the device with elevated privileges, potentially leading to full device compromise. The CVSS 4.0 score of 8.7 reflects the vulnerability's critical impact on confidentiality, integrity, and availability, combined with its low attack complexity and no requirement for privileges or user interaction. Although no confirmed exploitation in the wild has been reported, a public exploit has been released, increasing the risk of imminent attacks. The vulnerability affects a widely deployed consumer and small business networking device, which often serves as a gateway to internal networks, amplifying the potential damage. The lack of available patches at the time of disclosure means that organizations must rely on network-level mitigations and monitoring until firmware updates are released.

Potential Impact

For European organizations, exploitation of CVE-2025-12211 could result in unauthorized remote code execution on Tenda O3 devices, leading to full compromise of the affected routers. This can cause severe disruptions in network availability, interception or manipulation of sensitive data traversing the device, and potential lateral movement into internal networks. Critical infrastructure, small and medium enterprises, and home office environments using these devices are particularly vulnerable. The compromise of network gateways can undermine confidentiality and integrity of communications, facilitate persistent access for attackers, and enable further attacks such as data exfiltration or ransomware deployment. The remote, unauthenticated nature of the exploit increases the risk of widespread automated attacks targeting vulnerable devices across Europe. Additionally, the public availability of exploit code lowers the barrier for threat actors to weaponize this vulnerability rapidly.

Mitigation Recommendations

1. Immediately identify and inventory all Tenda O3 devices running firmware version 1.0.0.10(2478) within the network. 2. Monitor Tenda’s official channels for firmware updates addressing CVE-2025-12211 and apply patches as soon as they become available. 3. Until patches are released, implement network-level protections such as firewall rules or intrusion prevention system (IPS) signatures to block or alert on traffic targeting the /goform/setDmzInfo endpoint or suspicious dmzIP parameter manipulations. 4. Restrict remote management access to Tenda O3 devices by limiting access to trusted IP addresses and disabling remote administration if not required. 5. Conduct regular network traffic analysis to detect anomalous requests or exploitation attempts against the vulnerable endpoint. 6. Educate IT staff about the vulnerability and ensure incident response plans include steps for handling potential exploitation. 7. Consider segmenting networks to isolate vulnerable devices from critical assets to reduce potential impact. 8. Engage with vendors or third-party security providers for advanced detection and mitigation support if necessary.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
VulDB
Date Reserved
2025-10-25T11:59:09.592Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 68feefec79a7bb5513b9db5f

Added to database: 10/27/2025, 4:07:08 AM

Last enriched: 11/3/2025, 6:06:59 AM

Last updated: 12/9/2025, 10:41:29 AM

Views: 113

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats