CVE-2025-12234
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-10-27

Last updated on: 2025-10-27

Assigner: VulDB

Description
A vulnerability has been found in Tenda CH22 1.0.0.1. This affects the function fromSafeMacFilter of the file /goform/SafeMacFilter. The manipulation of the argument page leads to buffer overflow. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-10-27
Last Modified
2025-10-27
Generated
2026-05-07
AI Q&A
2025-10-27
EPSS Evaluated
2026-05-05
NVD
Affected Vendors & Products
Showing 2 associated CPEs
Vendor Product Version / Range
tenda ch22_firmware 1.0.0.1
tenda ch22 *
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
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-2025-12234 is a critical buffer overflow vulnerability in the Tenda CH22 router version 1.0.0.1, specifically in the fromSafeMacFilter function within the /goform/SafeMacFilter endpoint. The vulnerability occurs because the "page" parameter is processed using the unsafe sprintf function to write into a fixed-size 256-byte buffer without proper length validation. If an input larger than 256 bytes is supplied, it causes adjacent memory to be overwritten, leading to memory corruption. This can result in application crashes, arbitrary code execution, and information leakage. The vulnerability can be exploited remotely without authentication, making it highly critical. [1, 2, 3]


How can this vulnerability impact me? :

This vulnerability can severely impact you by allowing attackers to remotely exploit the router to cause application crashes (Denial of Service), execute arbitrary code, and leak sensitive information from device memory. Exploitation can lead to full control over the router, enabling attackers to monitor network traffic, disrupt device stability, compromise data confidentiality and integrity, and potentially use the device as a pivot point to attack other devices on the network. [1, 2, 3]


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability can be detected by checking if the Tenda CH22 router version 1.0.0.1 is present on your network and by testing the /goform/SafeMacFilter endpoint for buffer overflow conditions. A practical detection method is to send a POST request with an oversized "page" parameter (e.g., greater than 256 bytes) to the /goform/SafeMacFilter endpoint and observe if the device crashes, behaves abnormally, or returns errors indicating memory corruption. For example, using curl or similar tools, you can run a command like: curl -X POST -d "page=$(python3 -c 'print("A"*300)')" http://<router-ip>/goform/SafeMacFilter and monitor the device response or stability. Additionally, network monitoring tools can be used to detect unusual traffic patterns or crashes related to this endpoint. [3]


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include replacing the affected Tenda CH22 router with a different device or firmware version that is not vulnerable, as no known mitigations currently exist. If replacement is not immediately possible, restrict access to the /goform/SafeMacFilter endpoint by limiting network exposure, applying firewall rules to block unauthorized access, and monitoring for suspicious activity targeting this endpoint. Additionally, applying strict input validation and bounds checking on the "page" parameter in the firmware code (e.g., replacing sprintf with snprintf and enforcing a maximum input length of 256 bytes) is recommended for a long-term fix. Following secure coding practices and principle of least privilege for services handling this input can also reduce risk. [1, 3]


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart