CVE-2025-4446
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 vulnerability has been found in H3C GR-5400AX up to 100R008 and classified as critical. This vulnerability affects the function Edit_List_SSID of the file /goform/aspForm. The manipulation of the argument param leads to buffer overflow. The attack needs to be approached within the local network.
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 · moderate confidenceBuffer overflow vulnerability in H3C GR-5400AX routers (versions up to 100R008) in the Edit_List_SSID function of /goform/aspForm. The 'param' argument is not properly validated, allowing a local network attacker to overflow a buffer, potentially leading to code execution or denial of service.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:L/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.
-
Identify device modelAccess the router's web管理界面 (typically at 192.168.1.1) or log via SSH/Telnet and check the model information in the system status or device info pageAffected if Device is not an H3C GR-5400AX, then not affected by this specific CVE
-
Check firmware versionIn the router's web interface, navigate to System Settings or Status page to view the firmware version. Alternatively, access via CLI and use command like 'display version' or 'show firmware-version'Affected if Firmware version is 100R008 or lower (the vulnerability affects versions up to and including 100R008)
-
Verify Edit_List_SSID function exposureConfirm the router's web interface at /goform/aspForm is accessible from your network. This is the endpoint containing the vulnerable Edit_List_SSID functionAffected if The /goform/aspForm endpoint responds and accepts the 'param' argument, indicating the vulnerable function is exposed
-
Check network accessibility of management interfaceDetermine if the router's HTTP/HTTPS management port (typically 80/443) is listening on interfaces accessible to untrusted network segments. Use 'netstat -an' or similar to check listening ports and their bindingsAffected if The management web interface is reachable from network segments beyond trusted local users, increasing attack surface
You are affected if you have an H3C GR-5400AX router running firmware version 100R008 or lower, and the router's web management interface (/goform/aspForm) is accessible from your network where an attacker could send a crafted 'param' argument to trigger the buffer overflow in Edit_List_SSID.
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 vendor firmware update beyond version 100R008 when available. Restrict access to the device's management interface to trusted local network users only.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-4446 — 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-4446 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