# CVE-2022-48260: Memory corruption in BiSheng-WNM

> A buffer overflow in BiSheng-WNM firmware allows attackers to cause device service exceptions, impacting network availability.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Feb 2023
- **Updated:** 11 Mar 2025
- **Also known as:** GHSA-w5rv-9f58-c4f3

## What is CVE-2022-48260?

CVE-2022-48260 is a high-severity memory corruption vulnerability in BiSheng-WNM, published on 27 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

There is a buffer overflow vulnerability in BiSheng-WNM FW 3.0.0.325. Successful exploitation could lead to device service exceptions.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2022-48260?

It affects 1 product.


Products: Huawei Bisheng-Wnm Firmware.

## How do I fix CVE-2022-48260?

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

## Is CVE-2022-48260 being exploited?

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

## Other vulnerabilities in BiSheng-WNM

- [CVE-2022-48472](https://insights.sbomify.com/CVE-2022-48472/): Command injection in BiSheng-WNM (critical 9.8)
- [CVE-2022-48255](https://insights.sbomify.com/CVE-2022-48255/): Command injection in BiSheng-WNM (critical 9.8)
- [CVE-2022-48259](https://insights.sbomify.com/CVE-2022-48259/): Command injection in BiSheng-WNM (critical 9.8)
- [CVE-2022-48471](https://insights.sbomify.com/CVE-2022-48471/): Other in BiSheng-WNM (high 7.5)
- [CVE-2022-48473](https://insights.sbomify.com/CVE-2022-48473/): Other in BiSheng-WNM (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-48260 and fix it if it is affected.

What it is: CVE-2022-48260 is a high-severity memory corruption vulnerability in BiSheng-WNM, published on 27 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-48260 in the wild and no public exploit code.

Affected product: BiSheng-WNM. 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-2022-48260/ (Markdown: https://insights.sbomify.com/CVE-2022-48260/index.md)
```

## Sources

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

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