# CVE-2022-48469: Other in B535-232a

> Attackers can hijack network traffic on Huawei routers, allowing them to intercept or modify data packets.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **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:** 16 Jun 2023
- **Updated:** 17 Dec 2024
- **Also known as:** GHSA-84wq-7x6v-v62w

## What is CVE-2022-48469?

CVE-2022-48469 is a medium-severity vulnerability in Huawei B535-232a, published on 16 Jun 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

There is a traffic hijacking vulnerability in Huawei routers. Successful exploitation of this vulnerability can cause packets to be hijacked by attackers.

Weakness: CWE-290 (Authentication Bypass by Spoofing)

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

It affects 1 product.


Products: Huawei B535-232a Firmware.

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

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

## Is CVE-2022-48469 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-48469 is a medium-severity vulnerability in Huawei B535-232a, published on 16 Jun 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-48469 in the wild and no public exploit code.

Affected product: Huawei B535-232a. 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-48469/ (Markdown: https://insights.sbomify.com/CVE-2022-48469/index.md)
```

## Sources

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

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