# CVE-2018-6021: Command injection in n/a

> Attackers can execute arbitrary code remotely on Silex and GE smart home devices due to unsanitized system call parameters.

- **Severity:** High 7.4 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L`)
- **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:** 9 May 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-pw4x-2ppx-26rp

## What is CVE-2018-6021?

CVE-2018-6021 is a high-severity command injection vulnerability in n/a, published on 9 May 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Silex SD-320AN version 2.01 and prior and GE MobileLink(GEH-SD-320AN) version GEH-1.1 and prior have a system call parameter that is not properly sanitized, which may allow remote code execution.

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

## Which versions are affected by CVE-2018-6021?

It affects 2 products.


Products: Silextechnology Geh-Sd-320an Firmware, Silextechnology Sd-320an Firmware.

## How do I fix CVE-2018-6021?

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

## Is CVE-2018-6021 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-6021 and fix it if it is affected.

What it is: CVE-2018-6021 is a high-severity command injection vulnerability in n/a, published on 9 May 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-6021 in the wild and no public exploit code.

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

## Sources

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

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