# CVE-2025-6732: UTT HiPER 840G API setSysAdm strcpy buffer overflow

> Remote attackers can trigger a buffer overflow in the UTT HiPER 840G API via the passwd1 argument, potentially leading to code execution.

- **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:** 26 Jun 2025
- **Updated:** 27 Jun 2025
- **Also known as:** GHSA-x2fh-cm22-vr47

## What is CVE-2025-6732?

CVE-2025-6732 is a high-severity memory corruption vulnerability in UTT HiPER 840G, published on 26 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 UTT HiPER 840G up to 3.1.1-190328. It has been classified as critical. This affects the function strcpy of the file /goform/setSysAdm of the component API. The manipulation of the argument passwd1 leads to buffer overflow. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

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

It affects 1 product.


Products: Utt 840g Firmware.

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

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

## Is CVE-2025-6732 being exploited?

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

## Other vulnerabilities in UTT HiPER 840G

- [CVE-2025-11305](https://insights.sbomify.com/CVE-2025-11305/): UTT HiPER 840G formTaskEdit strcpy buffer overflow (high 8.7)
- [CVE-2025-10756](https://insights.sbomify.com/CVE-2025-10756/): UTT HiPER 840G getOneApConfTempEntry buffer overflow (high 8.7)
- [CVE-2025-7570](https://insights.sbomify.com/CVE-2025-7570/): UTT HiPER 840G aspRemoteApConfTempSend buffer overflow (high 8.7)
- [CVE-2025-7571](https://insights.sbomify.com/CVE-2025-7571/): UTT HiPER 840G aspApBasicConfigUrcp buffer overflow (high 8.7)
- [CVE-2025-7117](https://insights.sbomify.com/CVE-2025-7117/): UTT HiPER 840G websWhiteList buffer overflow (high 8.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-6732 is a high-severity memory corruption vulnerability in UTT HiPER 840G, published on 26 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-6732 exists.

Affected product: UTT HiPER 840G. 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-6732/ (Markdown: https://insights.sbomify.com/CVE-2025-6732/index.md)
```

## Sources

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

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