dbcve.org
Memory Buffer Bounds ErrorWeakness · CWE-119

CVE-2025-6090

HIGH · 8.8 CVSS v3.1 Published 2025-06-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
A vulnerability was found in H3C GR-5400AX V100R009L50 and classified as critical. This issue affects the function UpdateWanparamsMulti/UpdateIpv6params of the file /routing/goform/aspForm. The manipulation of the argument param leads to buffer overflow. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The vendor confirms the existence of this issue. Because they assess the risk as low, they do not have immediate plans for remediation.

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 confidence

A buffer overflow vulnerability exists in H3C GR-5400AX router firmware V100R009L50 in the UpdateWanparamsMulti and UpdateIpv6params functions within /routing/goform/aspForm. The param argument is not properly bounds-checked, allowing an attacker to overflow a buffer via specially crafted HTTP requests. This can be exploited remotely with network access to the device's management interface.

MitigationSince the vendor has not committed to immediate remediation, apply network segmentation to isolate the router, restrict management interface access to trusted IPs only via firewall rules, disable remote administration if WAN access is not required, and monitor for exploitation attempts.

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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm device model is H3C GR-5400AX
    Access the router web interface or CLI and identify the model number. Check the device label, web UI footer, or run 'show version' command via console/SSH.
    Affected if The device is an H3C GR-5400AX router.
  2. Identify installed firmware version
    Navigate to the router web UI status page, or run 'show version' via console/SSH to retrieve the firmware version string.
    Affected if The firmware version is V100R009L50 (or falls within the affected version range if additional versions are identified).
  3. Verify the web interface is enabled and accessible
    Attempt to reach the router's web interface over HTTP/HTTPS. Confirm the /routing/goform/aspForm endpoint responds to requests.
    Affected if The web interface is accessible on the network and the aspForm handler is reachable.
  4. Confirm WAN or IPv6 configuration features are active
    Check the router web UI under WAN settings or IPv6 settings. If these features are disabled, the vulnerable code paths may not be exercised.
    Affected if WAN configuration or IPv6 parameters features are enabled on the device.

If the device is an H3C GR-5400AX running firmware V100R009L50 with the web interface accessible and WAN/IPv6 features enabled, the environment is affected by this buffer overflow vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Since the vendor has not committed to immediate remediation, apply network segmentation to isolate the router, restrict management interface access to trusted IPs only via firewall rules, disable remote administration if WAN access is not required, and monitor for exploitation attempts.

Recommended fix Moderate confidence
  1. This vulnerability has no available remediation from the vendor.
  2. H3C has explicitly stated they do not have immediate plans to fix this issue.
  3. Consider replacing the affected H3C GR-5400AX router with a currently supported model from H3C or another vendor.
  4. If replacement is not possible, restrict network access to the router's management interface to trusted sources only using firewall rules.
  5. Disable remote management features if not required, limiting access to local network only.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-6090 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-6090 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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