# CVE-2020-8539: Command injection in n/a

> Attackers can inject unauthorized commands via the micomd daemon to trigger unintended vehicle functionalities and send CAN frames.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Dec 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-7g6h-m62g-mmqr

## What is CVE-2020-8539?

CVE-2020-8539 is a high-severity command injection vulnerability in n/a, published on 1 Dec 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Kia Motors Head Unit with Software version: SOP.003.30.18.0703, SOP.005.7.181019, and SOP.007.1.191209 may allow an attacker to inject unauthorized commands, by executing the micomd executable deamon, to trigger unintended functionalities. In addition, this executable may be used by an attacker to inject commands to generate CAN frames that are sent into the M-CAN bus (Multimedia CAN bus) of the vehicle.

Weakness: CWE-276 (Incorrect Default Permissions)

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

It affects 1 product.


Products: Kia Head Unit Firmware.

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

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

## Is CVE-2020-8539 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-8539 exists.

Public exploit code:

- KOFFEE - Kia OFFensivE Exploit (metasploit)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-8539 is a high-severity command injection vulnerability in n/a, published on 1 Dec 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-8539 exists.

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

## Sources

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

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