# CVE-2020-9527: Memory corruption in n/a

> Unauthenticated remote attackers can execute arbitrary code via a buffer overflow in the P2P service of millions of IoT 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:** 10 Aug 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-w59r-wjpf-fgqc

## What is CVE-2020-9527?

CVE-2020-9527 is a critical memory corruption vulnerability in n/a, published on 10 Aug 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Firmware developed by Shenzhen Hichip Vision Technology (V6 through V20, after 2018-08-09 through 2020), as used by many different vendors in millions of Internet of Things devices, suffers from buffer overflow vulnerability that allows unauthenticated remote attackers to execute arbitrary code via the peer-to-peer (P2P) service. This affects products marketed under the following brand names: Accfly, Alptop, Anlink, Besdersec, BOAVISION, COOAU, CPVAN, Ctronics, D3D Security, Dericam, Elex System, Elite Security, ENSTER, ePGes, Escam, FLOUREON, GENBOLT, Hongjingtian (HJT), ICAMI, Iegeek, Jecurity, Jennov, KKMoon, LEFTEK, Loosafe, Luowice, Nesuniq, Nettoly, ProElite, QZT, Royallite, SDETER, SV3C, SY2L, Tenvis, ThinkValue, TOMLOV, TPTEK, WGCC, and ZILINK.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

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

It affects 1 product.


Products: Hichip Shenzhen Hichip Vision Technology Firmware.

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

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

## Is CVE-2020-9527 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-9529](https://insights.sbomify.com/CVE-2020-9529/): Privilege escalation in n/a (critical 9.8)
- [CVE-2022-23382](https://insights.sbomify.com/CVE-2022-23382/): Denial of service in n/a (high 8.1)
- [CVE-2020-9528](https://insights.sbomify.com/CVE-2020-9528/): Weak cryptography in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-9527 is a critical memory corruption vulnerability in n/a, published on 10 Aug 2020. 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-2020-9527 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-9527/ (Markdown: https://insights.sbomify.com/CVE-2020-9527/index.md)
```

## Sources

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

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