# CVE-2022-41576: The rphone module has a script that can be maliciously modified.Successful exploitation of this vulnerability may cause irreversible program


- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 14 Oct 2022
- **Updated:** 14 May 2025
- **Also known as:** GHSA-qr89-xx7m-9qx6

## What is CVE-2022-41576?

CVE-2022-41576 is a high-severity vulnerability in Huawei Emui, published on 14 Oct 2022. 

### Official description

The rphone module has a script that can be maliciously modified.Successful exploitation of this vulnerability may cause irreversible programs to be implanted on user devices.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 2 products.


Products: Huawei Emui, Huawei Harmonyos.

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

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

## Is CVE-2022-41576 being exploited?

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

## Other vulnerabilities in Huawei Emui

- [CVE-2023-52370](https://insights.sbomify.com/CVE-2023-52370/): Memory corruption in EMUI (critical 9.8)
- [CVE-2023-52378](https://insights.sbomify.com/CVE-2023-52378/): Business logic in EMUI (critical 9.8)
- [CVE-2023-52381](https://insights.sbomify.com/CVE-2023-52381/): Code injection in EMUI (critical 9.8)
- [CVE-2023-52103](https://insights.sbomify.com/CVE-2023-52103/): Memory corruption in EMUI (critical 9.8)
- [CVE-2023-46773](https://insights.sbomify.com/CVE-2023-46773/): Privilege escalation in EMUI (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-41576 is a high-severity vulnerability in Huawei Emui, published on 14 Oct 2022. 
Exploitation: There is no known exploitation of CVE-2022-41576 in the wild and no public exploit code.

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

## Sources

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

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