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

> Attackers can eavesdrop on IoT devices using CS2 Network P2P to capture session data, credentials, and media streams.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 10 Aug 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-wm7x-g8j8-cw8f

## What is CVE-2020-9526?

CVE-2020-9526 is a medium-severity 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

CS2 Network P2P through 3.x, as used in millions of Internet of Things devices, suffers from an information exposure flaw that exposes user session data to supernodes in the network, as demonstrated by passively eavesdropping on user video/audio streams, capturing credentials, and compromising devices.

Weakness: CWE-327 (Use of a Broken or Risky Cryptographic Algorithm), CWE-319 (Cleartext Transmission of Sensitive Information)

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

It affects 1 product.


Products: Cs2-Network P2p.

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

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

## Is CVE-2020-9526 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-9525](https://insights.sbomify.com/CVE-2020-9525/): Auth bypass in n/a (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-9526 is a medium-severity 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-9526 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-9526/ (Markdown: https://insights.sbomify.com/CVE-2020-9526/index.md)
```

## Sources

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

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