# CVE-2020-6865: Information disclosure in OSCP

> Attackers can obtain sensitive internal error information from the ZTE SDN controller due to improper error handling.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Apr 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-836h-456r-hxj5

## What is CVE-2020-6865?

CVE-2020-6865 is a medium-severity vulnerability in OSCP, published on 30 Apr 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

ZTE SDN controller platform is impacted by an information leakage vulnerability. Due to the program's failure to optimize the response of failure to the request, the caller can directly view the internal error code location of the component. Attackers could exploit this vulnerability to obtain sensitive information. This affects: OSCP versions V16.19.10 and V16.19.20.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Zte Oscp.

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

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

## Is CVE-2020-6865 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-6865 is a medium-severity vulnerability in OSCP, published on 30 Apr 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-6865 in the wild and no public exploit code.

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

## Sources

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

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