# CVE-2021-32089: File upload in n/a

> Unauthenticated attackers can upload arbitrary files to Zebra FX9500 RFID readers, leading to code execution and information disclosure on unsupported devices.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 May 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-553c-2cmm-9m3c

## What is CVE-2021-32089?

CVE-2021-32089 is a critical vulnerability in n/a, published on 11 May 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered on Zebra (formerly Motorola Solutions) Fixed RFID Reader FX9500 devices. An unauthenticated attacker can upload arbitrary files to the filesystem that can then be accessed through the web interface. This can lead to information disclosure and code execution. NOTE: This vulnerability only affects products that are no longer supported by the maintainer

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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

It affects 1 product.


Products: Zebra Fx9500 Firmware.

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

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

## Is CVE-2021-32089 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-10875](https://insights.sbomify.com/CVE-2020-10875/): Path traversal in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-32089 is a critical vulnerability in n/a, published on 11 May 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-32089 in the wild and no public exploit code.

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

## Sources

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

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