# CVE-2017-10835: Code injection in n/a

> Authenticated attackers can execute arbitrary code on Dokodemo eye Smart HD cameras via unspecified injection vectors.

- **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:** 28 Aug 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-37rp-rg27-25p2

## What is CVE-2017-10835?

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

### Official description

"Dokodemo eye Smart HD" SCR02HD Firmware 1.0.3.1000 and earlier allows authenticated attackers to conduct code injection attacks via unspecified vectors.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Nippon-Antenna Scr02hd Firmware.

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

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

## Is CVE-2017-10835 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-10832](https://insights.sbomify.com/CVE-2017-10832/): Command injection in "Dokodemo eye Smart HD" SCR02HD (critical 9.8)
- [CVE-2017-10833](https://insights.sbomify.com/CVE-2017-10833/): Missing authorization in "Dokodemo eye Smart HD" SCR02HD (critical 9.1)
- [CVE-2017-10834](https://insights.sbomify.com/CVE-2017-10834/): Path traversal in "Dokodemo eye Smart HD" SCR02HD (medium 6.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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