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

> Remote unauthenticated attackers can execute arbitrary commands on Ichano AtHome IP Cameras via the noodles binary.

- **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:** No
- **Published:** 19 Dec 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-mhxf-r4fj-xrhr

## What is CVE-2017-17761?

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

### Official description

An issue was discovered on Ichano AtHome IP Camera devices. The device runs the "noodles" binary - a service on port 1300 that allows a remote (LAN) unauthenticated user to run arbitrary commands. This binary requires the "system" XML element for specifying the command. For example, a <system>id</system> command results in a <system_ack>ok</system_ack> response.

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

It affects 1 product.


Products: Ichano Athome Ip Camera Firmware.

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

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

## Is CVE-2017-17761 being exploited?

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

Public exploit code:

- Ichano AtHome IP Cameras - Multiple Vulnerabilities (exploitdb)
-  Simulação educacional de exploração de falha em dispositivos IoT com base no CVE-2017-17761 (github_poc): https://github.com/mirellesilvajs/iot-vuln-lab-cve-2017-17761

## Fix prompt for AI coding agents

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

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

## Sources

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

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