# CVE-2017-3853: Memory corruption in Cisco IOx

> Unauthenticated remote attackers can trigger a stack overflow in the Cisco IOx DMo process to execute arbitrary code with root privileges within the virtual instance.

- **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:** 22 Mar 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-q7j7-c4rf-9cfp

## What is CVE-2017-3853?

CVE-2017-3853 is a critical memory corruption vulnerability in Cisco IOx, published on 22 Mar 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in the Data-in-Motion (DMo) process installed with the Cisco IOx application environment could allow an unauthenticated, remote attacker to cause a stack overflow that could allow remote code execution with root privileges in the virtual instance running on an affected device. The vulnerability is due to insufficient bounds checking in the DMo process. An attacker could exploit this vulnerability by sending crafted packets that are forwarded to the DMo process for evaluation. The impacts of a successful exploit are limited to the scope of the virtual instance and do not impact the router that is hosting Cisco IOx. This vulnerability affects the following Cisco 800 Series Industrial Integrated Services Routers: Cisco IR809 and Cisco IR829. Cisco IOx Releases 1.0.0.0 and 1.1.0.0 are vulnerable. Cisco Bug IDs: CSCuy52330.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Cisco Iox.

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

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

## Is CVE-2017-3853 being exploited?

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

## Other vulnerabilities in Cisco IOx

- [CVE-2020-3238](https://insights.sbomify.com/CVE-2020-3238/): Cisco IOx Application Framework Arbitrary File Creation Vulnerability (high 8.1)
- [CVE-2017-3852](https://insights.sbomify.com/CVE-2017-3852/): Path traversal in Cisco Application-Hosting Framework (high 8.1)
- [CVE-2017-3851](https://insights.sbomify.com/CVE-2017-3851/): Path traversal in Cisco Application-Hosting Framework (high 7.5)
- [CVE-2016-9199](https://insights.sbomify.com/CVE-2016-9199/): Path traversal in Cisco IOx (medium 6.5)
- [CVE-2020-3233](https://insights.sbomify.com/CVE-2020-3233/): Cisco IOx Application Framework Local Manager Stored Cross-Site Scripting Vulnerability (medium 6.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-3853 is a critical memory corruption vulnerability in Cisco IOx, published on 22 Mar 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-3853 in the wild and no public exploit code.

Affected product: Cisco IOx. 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-3853/ (Markdown: https://insights.sbomify.com/CVE-2017-3853/index.md)
```

## Sources

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

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