# CVE-2020-7805: Command injection in KT Slim egg IML500

> Attackers can execute arbitrary OS commands on KT Slim egg IML500 and IML520 wifi devices via command injection.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 May 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-h8xc-cp2p-x3fc

## What is CVE-2020-7805?

CVE-2020-7805 is a critical command injection vulnerability in Infomark KT Slim egg IML500, published on 7 May 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered on KT Slim egg IML500 (R7283, R8112, R8424) and IML520 (R8112, R8368, R8411) wifi device. This issue is a command injection allowing attackers to execute arbitrary OS commands.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 2 products.


Products: Infomark Iml500 Firmware, Infomark Iml520 Firmware.

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

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

## Is CVE-2020-7805 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-7805 is a critical command injection vulnerability in Infomark KT Slim egg IML500, published on 7 May 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-7805 in the wild and no public exploit code.

Affected product: Infomark KT Slim egg IML500. 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-7805/ (Markdown: https://insights.sbomify.com/CVE-2020-7805/index.md)
```

## Sources

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

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