# CVE-2014-8387: Command injection in n/a

> Authenticated attackers can execute arbitrary commands on Advantech EKI-6340 access points via the pinghost parameter.

- **Severity:** Critical 9.0 (`AV:N/AC:L/Au:S/C:C/I:C/A:C`)
- **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:** 20 Nov 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-6xqg-q7p8-9r82

## What is CVE-2014-8387?

CVE-2014-8387 is a critical command injection vulnerability in n/a, published on 20 Nov 2014. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

cgi/utility.cgi in Advantech EKI-6340 2.05 Wi-Fi Mesh Access Point allows remote authenticated users to execute arbitrary commands via shell metacharacters in the pinghost parameter to ping.cgi.

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

## Which versions are affected by CVE-2014-8387?

It affects 2 products.


Products: Advantech Eki-6340, Advantech Eki-6340 Firmware.

## How do I fix CVE-2014-8387?

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

## Is CVE-2014-8387 being exploited?

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

Public exploit code:

- Advantech EKI-6340 - Command Injection (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-8387 and fix it if it is affected.

What it is: CVE-2014-8387 is a critical command injection vulnerability in n/a, published on 20 Nov 2014. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2014-8387 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-2014-8387/ (Markdown: https://insights.sbomify.com/CVE-2014-8387/index.md)
```

## Sources

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

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