# CVE-2017-3860: Memory corruption in Cisco IOS and IOS XE

> Unauthenticated remote attackers can cause a denial of service via buffer overflow in the EnergyWise module of Cisco IOS devices.

- **Severity:** High 8.6 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/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:** 20 Apr 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-f7gj-54hp-mr7v

## What is CVE-2017-3860?

CVE-2017-3860 is a high-severity memory corruption vulnerability in Cisco Ios, published on 20 Apr 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple vulnerabilities in the EnergyWise module of Cisco IOS (12.2 and 15.0 through 15.6) and Cisco IOS XE (3.2 through 3.18) could allow an unauthenticated, remote attacker to cause a buffer overflow condition or a reload of an affected device, leading to a denial of service (DoS) condition. These vulnerabilities are due to improper parsing of crafted EnergyWise packets destined to an affected device. An attacker could exploit these vulnerabilities by sending crafted EnergyWise packets to be processed by an affected device. An exploit could allow the attacker to cause a buffer overflow condition or a reload of the affected device, leading to a DoS condition. Cisco IOS Software and Cisco IOS XE Software support EnergyWise for IPv4 communication. Only IPv4 packets destined to a device configured as an EnergyWise domain member can trigger these vulnerabilities. IPv6 packets cannot be used to trigger these vulnerabilities. Cisco Bug ID CSCur29331.

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

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

It affects 2 products.


Products: Cisco Ios, Cisco Ios Xe.

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

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

## Is CVE-2017-3860 being exploited?

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

## Other vulnerabilities in Cisco Ios

- [CVE-2017-12240](https://insights.sbomify.com/CVE-2017-12240/): Cisco IOS and IOS XE Software DHCP Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2017-3881](https://insights.sbomify.com/CVE-2017-3881/): Cisco IOS and IOS XE Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2018-0167](https://insights.sbomify.com/CVE-2018-0167/): Cisco IOS, XR, and XE Software Buffer Overflow (high 8.8, exploited in the wild)
- [CVE-2017-6736](https://insights.sbomify.com/CVE-2017-6736/): Cisco IOS and IOS XE Software SNMP Remote Code Execution (high 8.8, exploited in the wild)
- [CVE-2017-6737](https://insights.sbomify.com/CVE-2017-6737/): Cisco IOS and IOS XE Software SNMP Remote Code Execution (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-3860 is a high-severity memory corruption vulnerability in Cisco Ios, published on 20 Apr 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-3860 in the wild and no public exploit code.

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

## Sources

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

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