# CVE-2020-9209: Privilege escalation in SMC2.0

> Attackers can escalate privileges by exploiting improper directory permissions in Huawei SMC2.0, compromising service integrity.

- **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:** 13 Jan 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-wqm8-5876-3578

## What is CVE-2020-9209?

CVE-2020-9209 is a medium-severity vulnerability in SMC2.0, published on 13 Jan 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

There is a privilege escalation vulnerability in SMC2.0 product. Some files in a directory of a module are located improperly. It does not apply the directory limitation. Attackers can exploit this vulnerability by crafting malicious file to launch privilege escalation. This can compromise normal service of affected products.

Weakness: CWE-862 (Missing Authorization)

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

It affects 1 product.


Products: Huawei Smc2.0 Firmware.

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

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

## Is CVE-2020-9209 being exploited?

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

## Other vulnerabilities in SMC2.0

- [CVE-2017-8213](https://insights.sbomify.com/CVE-2017-8213/): Denial of service in SMC2.0 (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-9209 is a medium-severity vulnerability in SMC2.0, published on 13 Jan 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-9209 in the wild and no public exploit code.

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

## Sources

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

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