# CVE-2021-22439: Deserialization in AnyOffice

> An attacker can execute remote malicious code and control the device via a deserialization vulnerability in Huawei AnyOffice.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/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:** 29 Jun 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-mv3h-rm7m-83qx

## What is CVE-2021-22439?

CVE-2021-22439 is a high-severity unsafe deserialization vulnerability in AnyOffice, published on 29 Jun 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

There is a deserialization vulnerability in Huawei AnyOffice V200R006C10. An attacker can construct a specific request to exploit this vulnerability. Successfully exploiting this vulnerability, the attacker can execute remote malicious code injection and to control the device.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2021-22439?

It affects 1 product.


Products: Huawei Anyoffice.

## How do I fix CVE-2021-22439?

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

## Is CVE-2021-22439 being exploited?

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

## Other vulnerabilities in AnyOffice

- [CVE-2016-8275](https://insights.sbomify.com/CVE-2016-8275/): Denial of service in AnyOffice V200R006C00 (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-22439 and fix it if it is affected.

What it is: CVE-2021-22439 is a high-severity unsafe deserialization vulnerability in AnyOffice, published on 29 Jun 2021. 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-2021-22439 in the wild and no public exploit code.

Affected product: AnyOffice. 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-2021-22439/ (Markdown: https://insights.sbomify.com/CVE-2021-22439/index.md)
```

## Sources

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

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