# CVE-2020-11834: Memory corruption in OPPO Find X2

> A missing length check in the OPPO charger driver allows attackers to trigger memory corruption, potentially leading to code execution or privilege escalation on Find X2 devices.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Dec 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-9vr7-48xw-7c8q

## What is CVE-2020-11834?

CVE-2020-11834 is a medium-severity memory corruption vulnerability in OPPO Find X2, published on 31 Dec 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In /SM8250_Q_Master/android/vendor/oppo_charger/oppo/oppo_vooc.c, the function proc_fastchg_fw_update_write in proc_fastchg_fw_update_write does not check the parameter len, resulting in a vulnerability.

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 2 products.


Products: Oppo Find X2 Pro Firmware, Oppo Reno3 Pro Firmware.

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

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

## Is CVE-2020-11834 being exploited?

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

## Other vulnerabilities in OPPO Find X2

- [CVE-2020-11832](https://insights.sbomify.com/CVE-2020-11832/): Memory corruption in OPPO Find X2 (medium 5.5)
- [CVE-2020-11833](https://insights.sbomify.com/CVE-2020-11833/): Memory corruption in OPPO Find X2 (medium 5.5)
- [CVE-2020-11835](https://insights.sbomify.com/CVE-2020-11835/): Memory corruption in OPPO Find X2 (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-11834 is a medium-severity memory corruption vulnerability in OPPO Find X2, published on 31 Dec 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-11834 in the wild and no public exploit code.

Affected product: OPPO Find X2. 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-11834/ (Markdown: https://insights.sbomify.com/CVE-2020-11834/index.md)
```

## Sources

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

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