Raw vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XSummary
CVE-2025-11117 is a high-severity Improper Restriction of Operations within the Bounds of a Memory Buffer (CWE-119) vulnerability in Tenda Ch22 Firmware. Its CVSS base score is 7.4 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 49% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-11117 is a buffer overflow vulnerability in Tenda CH22 firmware version 1.0.0.1. The flaw affects the formWrlExtraGet function in the /goform/GstDhcpSetSer file, where manipulation of the "dips" argument triggers the overflow. Associated with CWE-119 and CWE-120, it was published on 2025-09-28 and carries a CVSS v3.1 base score of 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H).
The vulnerability is remotely exploitable over the network with low attack complexity and requires only low privileges from the attacker, with no user interaction needed. Successful exploitation can result in high impacts to confidentiality, integrity, and availability, potentially enabling arbitrary code execution or full device compromise.
Advisories referenced in VulDB entries (ctiid.326198, id.326198, submit.662927) and a GitHub issue (zhaoyinshan/CVE/issues/2) describe the issue and note that an exploit has been publicly disclosed and may be utilized. The vendor's site (tenda.com.cn) is listed among references, though specific patch details are not outlined in available information.
The public disclosure of the exploit code elevates the risk for unpatched Tenda CH22 devices exposed to the internet.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-31473
Vulnerability Data
A vulnerability was determined in Tenda CH22 1.0.0.1. This vulnerability affects the function formWrlExtraGet of the file /goform/GstDhcpSetSer. This manipulation of the argument dips causes buffer overflow. The attack is possible to be carried out remotely. The exploit has been…
more
publicly disclosed and may be utilized.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V17.3.2V5.2.1
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and analysis can find missing size checks before deployment.
Input validation directly enforces size checks before buffer copies.
Secure engineering principles require memory-safe design and coding that structurally avoids buffer-boundary violations.
Memory protection restricts exploitation impact of buffer overflows without eliminating the underlying coding flaw.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices (bounds checking, safe APIs, reviews) directly prevent this class of flaw.
Vulnerability scanning and code analysis directly surface buffer-boundary flaws.
Receiving and triaging vulnerability disclosures commonly includes buffer-related reports.
Developer training on secure coding reduces introduction of memory-buffer errors.
Patching replaces vulnerable code containing buffer-boundary defects.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Secure coding directly requires bounds-checked memory operations, addressing the root cause of CWE-120.
Security testing in development catches out-of-bounds accesses before release, covering most instances of the weakness.
Secure development lifecycle mandates memory-safety practices that directly prevent buffer-boundary violations.
Application security requirements can specify memory-safety rules, but do not prescribe implementation details.
Secure architecture and engineering principles include memory-safe design patterns that mitigate buffer overflows.