# CVE-2017-11366: Codiad Vulnerable to Shell Command Injection

> Remote attackers can execute arbitrary shell commands via embedded parameters in the file manager component of Codiad.

- **Severity:** Critical 9.8 (`CVSS:3.0/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:** Yes
- **Published:** 21 Aug 2017
- **Updated:** 5 Aug 2024
- **Also known as:** CVE-2017-1000124, CVE-2017-1000165, GHSA-jccv-3h4x-35mv

## What is CVE-2017-11366?

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

### Official description

components/filemanager/class.filemanager.php in Codiad before 2.8.4 is vulnerable to remote command execution because shell commands can be embedded in parameter values, as demonstrated by search_file_type.

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

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

2 open source packages ship an affected version, including codiad/codiad. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `codiad/codiad` | Packagist | All versions | 2.8.3 |
| `codiad/codiad` | Packagist | All versions | 2.8.3 |

Products: Codiad Codiad.

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

Upgrade codiad/codiad to 2.8.3 or later.

## Is CVE-2017-11366 being exploited?

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

Public exploit code:

- Codiad through 2.8.4 allows Remote Code Execution, a different vulnerability than CVE-2017-11366 and CVE-2017-15689 (github_poc): https://github.com/lolameroo/Codiad-CVE-2018-14009

## Other vulnerabilities in n/a

- [CVE-2019-19208](https://insights.sbomify.com/CVE-2019-19208/): Code injection in codiad (critical 9.8)
- [CVE-2018-14009](https://insights.sbomify.com/CVE-2018-14009/): Codiad remote code execution vulnerability (critical 9.8)
- [CVE-2020-14043](https://insights.sbomify.com/CVE-2020-14043/): Codiad CSRF Vulnerability (high 8.8)
- [CVE-2020-23355](https://insights.sbomify.com/CVE-2020-23355/): Codiad Vulnerable to PHP Magic Hash Vulnerability (high 7.5)
- [CVE-2017-1000125](https://insights.sbomify.com/CVE-2017-1000125/): File upload in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-11366 is a critical command injection vulnerability in n/a, published on 21 Aug 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-11366 in the wild and no public exploit code.

Affected packages and fixed versions:
- codiad/codiad (Packagist): affected all versions; fixed in 2.8.3
- codiad/codiad (Packagist): affected all versions; fixed in 2.8.3

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

## Sources

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

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