# CVE-2018-20523: Information disclosure in n/a

> A malicious app can read the user's cleartext browser history via content provider injection in Xiaomi Stock Browser.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Jun 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-rgf9-4gwx-vwv9

## What is CVE-2018-20523?

CVE-2018-20523 is a medium-severity vulnerability in n/a, published on 7 Jun 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Xiaomi Stock Browser 10.2.4.g on Xiaomi Redmi Note 5 Pro devices and other Redmi Android phones allows content provider injection. In other words, a third-party application can read the user's cleartext browser history via an app.provider.query content://com.android.browser.searchhistory/searchhistory request.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

## Which versions are affected by CVE-2018-20523?

It affects 19 products.


Products: Mi Redmi 4a Firmware, Mi Redmi 5 Plus Firmware, Mi Redmi 6 Firmware, Mi Redmi 6a Firmware, Mi Redmi 7 Firmware, Mi Redmi 7a Firmware, Mi Redmi Go Firmware, Mi Redmi K20 Firmware, Mi Redmi K20 Pro Firmware, Mi Redmi Note 4 Firmware, Mi Redmi Note 5 Firmware, Mi Redmi Note 5 Pro Firmware, Mi Redmi Note 5a Prime Firmware, Mi Redmi Note 6 Pro Firmware, Mi Redmi Note 7 Firmware, Mi Redmi Note 7s Firmware, Mi Redmi S2 Firmware, Mi Redmi Y3 Firmware, Mi Stock Browser.

## How do I fix CVE-2018-20523?

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

## Is CVE-2018-20523 being exploited?

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

Public exploit code:

- Xiaomi browser 10.2.4.g - Browser Search History Disclosure (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-20523 and fix it if it is affected.

What it is: CVE-2018-20523 is a medium-severity vulnerability in n/a, published on 7 Jun 2019. 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-2018-20523 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-2018-20523/ (Markdown: https://insights.sbomify.com/CVE-2018-20523/index.md)
```

## Sources

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

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