# CVE-2016-9216: Denial of service in Cisco ASR 5000 Software

> Remote unauthenticated attackers can cause a denial of service in the ipsecmgr process of Cisco ASR 5000 devices by sending malformed IKE packets.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Jan 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-mjwr-2f4h-2wmg

## What is CVE-2016-9216?

CVE-2016-9216 is a medium-severity denial of service vulnerability in Cisco ASR 5000 Software, published on 26 Jan 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An IKE Packet Parsing Denial of Service Vulnerability in the ipsecmgr process of Cisco ASR 5000 Software could allow an unauthenticated, remote attacker to cause the ipsecmgr process to reload. More Information: CSCuy06917 CSCuy45036 CSCuy59525. Known Affected Releases: 20.0.0 20.0.M0.62842 20.0.v0 20.0.M0.63229 20.1.0 20.1.a0 20.1.v0 21.0.0 21.0.v0. Known Fixed Releases: 20.0.0 20.0.0.63250 20.0.M0.63148 20.0.R0.63294 20.0.R0.63316 20.0.V0.63170 20.0.VG0.63188 20.0.v0 20.0.v0.64175 20.0.vg0.63522 20.1.A0.63166 20.2.A0.63174 20.1.A0.63232 20.2.A0.63237 20.0.M0.63226 20.0.M0.63229 20.0.R0.63294 20.0.R0.63316 20.0.V0.63263 20.0.VG0.63233 20.0.v0 20.0.v0.64175 20.0.vg0.63522 20.1.0 20.1.0.63959 20.1.M0.63876 20.1.T0.63886 20.1.V0.64231 20.1.VA0.64194 20.1.VB0.64210 20.1.a0 20.1.a0.64023 20.1.v0 20.1.v0.64607 20.2.A0.63895 21.0.0 21.0.0.65256 21.0.M0.63881 21.0.M0.64281 21.0.PP0.64366 21.0.V0.65052 21.0.v0 21.0.v0.65831 21.0.vb0.65887 21.1.R0.65130 21.1.R0.65135.

Weakness: CWE-399

## Which versions are affected by CVE-2016-9216?

It affects 1 product.


Products: Cisco Asr 5000 Series Software.

## How do I fix CVE-2016-9216?

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

## Is CVE-2016-9216 being exploited?

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

## Other vulnerabilities in Cisco ASR 5000 Software

- [CVE-2017-3819](https://insights.sbomify.com/CVE-2017-3819/): Privilege escalation in Cisco StarOS (high 8.8)
- [CVE-2017-6612](https://insights.sbomify.com/CVE-2017-6612/): Open redirect in Cisco ASR 5000 Series Aggregation Services Routers (high 8.6)
- [CVE-2017-6672](https://insights.sbomify.com/CVE-2017-6672/): Security feature bypass in Cisco ASR 5000 Series Aggregation Services Routers (high 7.5)
- [CVE-2016-6467](https://insights.sbomify.com/CVE-2016-6467/): Denial of service in Cisco Aggregation Services Router (ASR) 5000 Series Switch (high 7.5)
- [CVE-2016-9203](https://insights.sbomify.com/CVE-2016-9203/): Denial of service in Cisco ASR 5000 (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-9216 and fix it if it is affected.

What it is: CVE-2016-9216 is a medium-severity denial of service vulnerability in Cisco ASR 5000 Software, published on 26 Jan 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-2016-9216 in the wild and no public exploit code.

Affected product: Cisco ASR 5000 Software. 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-2016-9216/ (Markdown: https://insights.sbomify.com/CVE-2016-9216/index.md)
```

## Sources

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

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