# CVE-2022-48681: Memory corruption in EGRT-00

> A memory overflow in Huawei smart speakers can cause certain functions to fail, potentially leading to denial of service.

- **Severity:** High 7.2 (`CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 28 May 2024
- **Updated:** 3 Aug 2024

## What is CVE-2022-48681?

CVE-2022-48681 is a high-severity memory corruption vulnerability in Huawei EGRT-00, published on 28 May 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Some Huawei smart speakers have a memory overflow vulnerability. Successful exploitation of this vulnerability may cause certain functions to fail.

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-2022-48681?

It affects 1 product.


Products: Huawei Egrt-00 Firmware.

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

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

## Is CVE-2022-48681 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-48681 is a high-severity memory corruption vulnerability in Huawei EGRT-00, published on 28 May 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-48681 in the wild and no public exploit code.

Affected product: Huawei EGRT-00. 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-48681/ (Markdown: https://insights.sbomify.com/CVE-2022-48681/index.md)
```

## Sources

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

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