CVE-2025-12272
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA security flaw has been discovered in Tenda CH22 1.0.0.1. This impacts the function fromAddressNat of the file /goform/addressNat. Performing a manipulation of the argument page results in buffer overflow. The attack may be initiated remotely. The exploit has been released to the public and may be used for attacks.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA buffer overflow vulnerability exists in the Tenda CH22 router firmware 1.0.0.1 within the fromAddressNat function of /goform/addressNat. The 'page' parameter is not properly validated before use in a memory copy operation, allowing an attacker to overflow a fixed-size buffer and potentially achieve remote code execution on the device.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.0.0.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Tenda CH22 router modelAccess the router web admin interface (typically at 192.168.0.1 or 192.168.1.1) and check the device model information in the Status or System settings page. Alternatively, check the device label on the physical router hardware.Affected if The device model is not Tenda CH22, the vulnerability does not apply.
-
Check installed firmware versionIn the router web admin interface, navigate to System Settings > Firmware Upgrade or Status page and locate the firmware version field. Note the exact version number displayed.Affected if The installed firmware version is exactly 1.0.0.1 - this is the only affected version per the CVE.
-
Verify /goform/addressNat endpoint accessibilitySend an HTTP GET request to http://<router-ip>/goform/addressNat using a tool like curl or a browser. If the page loads or returns any response (even an authentication redirect), the endpoint exists and may be reachable.Affected if The endpoint responds and the router web interface is accessible from your network, the attack surface exists.
-
Check if NAT functionality is enabledIn the router web admin interface, navigate to Advanced Settings > NAT or Address NAT settings. Verify whether the NAT feature is currently enabled or configured.Affected if NAT functionality is enabled, the vulnerable fromAddressNat function is active and the device is potentially exploitable.
A Tenda CH22 router running firmware version 1.0.0.1 with the /goform/addressNat web interface accessible and NAT functionality enabled is affected by this vulnerability.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply available firmware updates from Tenda; if no update exists, disable remote administration or place the device behind a firewall to limit exposure to the web interface.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-12272 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-12272 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data