# CVE-2022-22259: Auth bypass in FLMG-10

> Improper authentication in Huawei FLMG-10 allows attackers to gain control of the victim device.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jun 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-qgj6-qhv7-vrfw

## What is CVE-2022-22259?

CVE-2022-22259 is a medium-severity authentication bypass vulnerability in FLMG-10, published on 13 Jun 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

There is an improper authentication vulnerability in FLMG-10 10.0.1.0(H100SP22C00). Successful exploitation of this vulnerability may lead to a control of the victim device.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Huawei Flmg-10 Firmware.

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

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

## Is CVE-2022-22259 being exploited?

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

## Other vulnerabilities in FLMG-10

- [CVE-2022-48330](https://insights.sbomify.com/CVE-2022-48330/): Memory corruption in FLMG-10 (high 8.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-22259 is a medium-severity authentication bypass vulnerability in FLMG-10, published on 13 Jun 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-22259 in the wild and no public exploit code.

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

## Sources

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

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