# CVE-2017-6079: Command injection in n/a

> A hidden page in the Edgemarc web interface allows attackers to execute arbitrary system commands, effectively acting as a web shell.

- **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:** 16 May 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-4w4r-mv2h-54x5

## What is CVE-2017-6079?

CVE-2017-6079 is a critical command injection vulnerability in n/a, published on 16 May 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The HTTP web-management application on Edgewater Networks Edgemarc appliances has a hidden page that allows for user-defined commands such as specific iptables routes, etc., to be set. You can use this page as a web shell essentially to execute commands, though you get no feedback client-side from the web application: if the command is valid, it executes. An example is the wget command. The page that allows this has been confirmed in firmware as old as 2006.

## Which versions are affected by CVE-2017-6079?

It affects 1 product.


Products: Ribboncommunications Edgemarc Firmware.

## How do I fix CVE-2017-6079?

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

## Is CVE-2017-6079 being exploited?

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

Public exploit code:

- https://github.com/MostafaSoliman/CVE-2017-6079-Blind-Command-Injection-In-Edgewater-Edgemarc-Devices-Exploit (github_poc): https://github.com/MostafaSoliman/CVE-2017-6079-Blind-Command-Injection-In-Edgewater-Edgemarc-Devices-Exploit

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-6079 and fix it if it is affected.

What it is: CVE-2017-6079 is a critical command injection vulnerability in n/a, published on 16 May 2017. 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-2017-6079 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-2017-6079/ (Markdown: https://insights.sbomify.com/CVE-2017-6079/index.md)
```

## Sources

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

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