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

> Authenticated attackers can execute arbitrary commands on D-Link EyeOn Baby Monitors via malicious HTTP requests.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 24 Aug 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-57rr-3xrx-whx2

## What is CVE-2017-11564?

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

### Official description

The D-Link EyeOn Baby Monitor (DCS-825L) 1.08.1 has multiple command injection vulnerabilities in the web service framework. An attacker can forge malicious HTTP requests to execute commands; authentication is required before executing the attack.

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 1 product.


Products: Dlink Eyeon Baby Monitor Firmware.

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

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

## Is CVE-2017-11564 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-11563](https://insights.sbomify.com/CVE-2017-11563/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-11564 is a high-severity command injection vulnerability in n/a, published on 24 Aug 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-2017-11564 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-11564/ (Markdown: https://insights.sbomify.com/CVE-2017-11564/index.md)
```

## Sources

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

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