# CVE-2020-9531: Code injection in n/a

> An attacker with NFC proximity can trigger code execution and data leakage in Xiaomi GetApps via malicious URL parameters.

- **Severity:** High 7.3 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 6 Mar 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-fwhf-m439-4q37

## What is CVE-2020-9531?

CVE-2020-9531 is a high-severity code injection vulnerability in n/a, published on 6 Mar 2020. 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

An issue was discovered on Xiaomi MIUI V11.0.5.0.QFAEUXM devices. In the Web resources of GetApps(com.xiaomi.mipicks), the parameters passed in are read and executed. After reading the resource files, relevant components open the link of the incoming URL. Although the URL is safe and can pass security detection, the data carried in the parameters are loaded and executed. An attacker can use NFC tools to get close enough to a user's unlocked phone to cause apps to be installed and information to be leaked. This is fixed on version: 2001122.

## Which versions are affected by CVE-2020-9531?

It affects 1 product.


Products: Mi Miui Firmware.

## How do I fix CVE-2020-9531?

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

## Is CVE-2020-9531 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-9530](https://insights.sbomify.com/CVE-2020-9530/): Information disclosure in n/a (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-9531 and fix it if it is affected.

What it is: CVE-2020-9531 is a high-severity code injection vulnerability in n/a, published on 6 Mar 2020. 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-2020-9531 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-2020-9531/ (Markdown: https://insights.sbomify.com/CVE-2020-9531/index.md)
```

## Sources

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

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