# CVE-2025-3854: H3C GR-3000AX HTTP POST Request aspForm Edit_List_SSID buffer overflow

> A buffer overflow in the HTTP POST handler allows local attackers to execute arbitrary code on H3C GR-3000AX routers.

- **Severity:** High 8.6 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Apr 2025
- **Updated:** 22 Apr 2025
- **Also known as:** GHSA-ph7f-wjp5-4mjj

## What is CVE-2025-3854?

CVE-2025-3854 is a high-severity memory corruption vulnerability in H3C GR-3000AX, published on 22 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability, which was classified as critical, was found in H3C GR-3000AX up to V100R006. Affected is the function EnableIpv6/UpdateWanModeMulti/UpdateIpv6Params/EditWlanMacList/Edit_List_SSID of the file /goform/aspForm of the component HTTP POST Request Handler. The manipulation of the argument param leads to buffer overflow. The attack needs to be initiated within the local network. The exploit has been disclosed to the public and may be used. It is recommended to upgrade the affected component. Other functions might be affected as well.

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-3854?


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

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

## Is CVE-2025-3854 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-3854 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-3854 is a high-severity memory corruption vulnerability in H3C GR-3000AX, published on 22 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-3854 exists.

Affected product: H3C GR-3000AX. 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-3854/ (Markdown: https://insights.sbomify.com/CVE-2025-3854/index.md)
```

## Sources

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

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