CVE Alert: CVE-2025-12232 – Tenda – CH22

CVE-2025-12232

HIGHNo exploitation known

A vulnerability was detected in Tenda CH22 1.0.0.1. Affected by this vulnerability is the function fromSafeClientFilter of the file /goform/SafeClientFilter. Performing manipulation of the argument page results in buffer overflow. The attack can be initiated remotely. The exploit is now public and may be used.

CVSS v3.1 (8.8)
Vendor
Tenda
Product
CH22
Versions
1.0.0.1
CWE
CWE-120, Buffer Overflow
Vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:P/RL:X/RC:R
Published
2025-10-27T06:22:13.528Z
Updated
2025-10-27T06:22:13.528Z

AI Summary Analysis

Risk verdict

High risk with a remotely exploitable buffer overflow on Tenda CH22 1.0.0.1; public exploit available, enabling remote code execution without user interaction.

Why this matters

Compromise of the router could give an attacker control over network traffic, data exfiltration, credential theft, or peer-device lateral movement into trusted networks. Small office and consumer deployments are particularly exposed where devices are internet-facing or poorly segmented.

Most likely attack path

An attacker can trigger the vulnerability over the network (AV:N, AC:L) with minimal prerequisites (PR:L, UI:N). Successful exploitation yields high-impact outcomes (C/H, I/H, A/H) within the affected device, with likely lateral movement limited mainly by device and network segmentation (Scope S:N). Public PoC and exploit availability increase the likelihood of opportunistic, automated exploitation.

Who is most exposed

Devices in home or small-business environments using Tenda CH22 are at risk, especially where devices are reachable from the internet or are poorly isolated from critical networks.

Detection ideas

  • Monitor for repeated attempts to access /goform/SafeClientFilter or related endpoints.
  • Look for sudden device reboots, crashes, or memory-corruption indicators in router logs.
  • IDS/IPS signatures matching known exploitation patterns or payloads.
  • Unusual spikes in traffic or new outbound connections from the router.

Mitigation and prioritisation

  • Apply vendor patch or firmware update to a non-affected build; verify integrity before deployment.
  • Disable or tightly restrict remote administration; enforce strong access controls and management access only from trusted networks.
  • Implement network segmentation to isolate IoT/router from critical assets; restrict east-west movement.
  • Review and harden firewall rules, disable unnecessary services on the device.
  • Document change control and test impact in a pilot before mass rollout.

Support Our Work

A considerable amount of time and effort goes into maintaining this website, creating backend automation and creating new features and content for you to make actionable intelligence decisions. Everyone that supports the site helps enable new functionality.

If you like the site, please support us on Patreon or Buy Me A Coffee using the buttons below.

AI APIs OSINT driven New features