# CVE-2020-9206: Information disclosure in eUDC660

> A high-privilege attacker can exploit improper resource management to obtain key files and decrypt data, compromising device confidentiality.

- **Severity:** Medium 6.7 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Mar 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-7j3j-77m4-qcrp

## What is CVE-2020-9206?

CVE-2020-9206 is a medium-severity vulnerability in eUDC660, published on 22 Mar 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The eUDC660 product has a resource management vulnerability. An attacker with high privilege needs to perform specific operations to exploit the vulnerability on the affected device. Due to improper resource management of the device, as a result, the key file can be obtained and data can be decrypted, affecting confidentiality, integrity, and availability of the device.

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

It affects 1 product.


Products: Huawei Eudc660 Firmware.

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

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

## Is CVE-2020-9206 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-9206 is a medium-severity vulnerability in eUDC660, published on 22 Mar 2021. 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-9206 in the wild and no public exploit code.

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

## Sources

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

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