# CVE-2020-9530: Information disclosure in n/a

> Attackers can leak information by inducing users to open specific web pages that trigger malicious WebView loading in the Messaging app via GetApps.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **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-px7h-6j69-959r

## What is CVE-2020-9530?

CVE-2020-9530 is a medium-severity vulnerability in n/a, published on 6 Mar 2020. An attacker can exploit it over the internet without logging in, 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. The export component of GetApps(com.xiaomi.mipicks) mishandles the functionality of opening other components. Attackers need to induce users to open specific web pages in a specific network environment. By jumping to the WebView component of Messaging(com.android.MMS) and loading malicious web pages, information leakage can occur. This is fixed on version: 2001122; 11.0.1.54.

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

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

It affects 1 product.


Products: Mi Miui Firmware.

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

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

## Is CVE-2020-9530 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-9531](https://insights.sbomify.com/CVE-2020-9531/): Code injection in n/a (high 7.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-9530 is a medium-severity vulnerability in n/a, published on 6 Mar 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-9530 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-9530/ (Markdown: https://insights.sbomify.com/CVE-2020-9530/index.md)
```

## Sources

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

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