# CVE-2025-6090: H3C GR-5400AX aspForm UpdateIpv6params buffer overflow

> Remote attackers can trigger a buffer overflow in the H3C GR-5400AX router's IPv6 parameter update function, potentially leading to code execution or service disruption.

- **Severity:** High 8.7 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Jun 2025
- **Updated:** 16 Jun 2025
- **Also known as:** GHSA-h95r-rh3q-w5w3

## What is CVE-2025-6090?

CVE-2025-6090 is a high-severity memory corruption vulnerability in H3C GR-5400AX, published on 15 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2025-6090?


## How do I fix CVE-2025-6090?

No fix has been published for CVE-2025-6090 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-6090 being exploited?

There is no known exploitation of CVE-2025-6090 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-6090 and fix it if it is affected.

What it is: CVE-2025-6090 is a high-severity memory corruption vulnerability in H3C GR-5400AX, published on 15 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-6090 in the wild and no public exploit code.

Affected product: H3C GR-5400AX. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-6090/ (Markdown: https://insights.sbomify.com/CVE-2025-6090/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-6090
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-6090
- OSV: https://osv.dev/vulnerability/CVE-2025-6090

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-6090/
Summaries are generated and may contain mistakes; the official description above is the record.