# CVE-2018-0369: Denial of service in Cisco StarOS unknown

> Remote attackers can cause a denial of service by sending malicious fragmented IPv4 packets to Cisco StarOS virtual platforms, triggering process restarts.

- **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:** 16 Jul 2018
- **Updated:** 29 Nov 2024
- **Also known as:** GHSA-cmmh-whh8-pwmv

## What is CVE-2018-0369?

CVE-2018-0369 is a high-severity denial of service vulnerability in Cisco StarOS unknown, published on 16 Jul 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in the reassembly logic for fragmented IPv4 packets of Cisco StarOS running on virtual platforms could allow an unauthenticated, remote attacker to trigger a reload of the npusim process, resulting in a denial of service (DoS) condition. There are four instances of the npusim process running per Service Function (SF) instance, each handling a subset of all traffic flowing across the device. It is possible to trigger a reload of all four instances of the npusim process around the same time. The vulnerability is due to improper handling of fragmented IPv4 packets containing options. An attacker could exploit this vulnerability by sending a malicious IPv4 packet across an affected device. An exploit could allow the attacker to trigger a restart of the npusim process, which will result in all traffic queued toward this instance of the npusim process to be dropped while the process is restarting. The npusim process typically restarts within less than a second. This vulnerability affects: Cisco Virtualized Packet Core-Single Instance (VPC-SI), Cisco Virtualized Packet Core-Distributed Instance (VPC-DI), Cisco Ultra Packet Core (UPC). Cisco Bug IDs: CSCvh29613.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2018-0369?

It affects 1 product.


Products: Cisco Staros.

## How do I fix CVE-2018-0369?

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

## Is CVE-2018-0369 being exploited?

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

## Other vulnerabilities in Cisco StarOS unknown

- [CVE-2023-20046](https://insights.sbomify.com/CVE-2023-20046/): Auth bypass in Cisco ASR 5000 Series Software (high 8.8)
- [CVE-2019-1869](https://insights.sbomify.com/CVE-2019-1869/): Cisco StarOS Denial of Service Vulnerability (high 8.6)
- [CVE-2017-6707](https://insights.sbomify.com/CVE-2017-6707/): Command injection in Cisco StarOS (high 8.2)
- [CVE-2021-1539](https://insights.sbomify.com/CVE-2021-1539/): Cisco ASR 5000 Series Software Authorization Bypass Vulnerabilities (high 8.1)
- [CVE-2021-1540](https://insights.sbomify.com/CVE-2021-1540/): Cisco ASR 5000 Series Software Authorization Bypass Vulnerabilities (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-0369 and fix it if it is affected.

What it is: CVE-2018-0369 is a high-severity denial of service vulnerability in Cisco StarOS unknown, published on 16 Jul 2018. 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-2018-0369 in the wild and no public exploit code.

Affected product: Cisco StarOS unknown. 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-2018-0369/ (Markdown: https://insights.sbomify.com/CVE-2018-0369/index.md)
```

## Sources

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

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