# CVE-2023-2676: H3C R160 aspForm stack-based overflow

> A stack-based buffer overflow in the H3C R160 router allows attackers to execute arbitrary code via the goForm/aspForm endpoint.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **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:** 12 May 2023
- **Updated:** 24 Jan 2025
- **Also known as:** GHSA-hr29-c6qg-4rw4

## What is CVE-2023-2676?

CVE-2023-2676 is a medium-severity memory corruption vulnerability in H3C R160, published on 12 May 2023. 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, has been found in H3C R160 V1004004. Affected by this issue is some unknown functionality of the file /goForm/aspForm. The manipulation of the argument go leads to stack-based buffer overflow. The exploit has been disclosed to the public and may be used. VDB-228890 is the identifier assigned to this vulnerability.

Weakness: CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2023-2676?

It affects 1 product.


Products: H3c Magic R160 Firmware.

## How do I fix CVE-2023-2676?

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

## Is CVE-2023-2676 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-2676 and fix it if it is affected.

What it is: CVE-2023-2676 is a medium-severity memory corruption vulnerability in H3C R160, published on 12 May 2023. 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-2023-2676 exists.

Affected product: H3C R160. 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-2023-2676/ (Markdown: https://insights.sbomify.com/CVE-2023-2676/index.md)
```

## Sources

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

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