# CVE-2017-6613: Denial of service in Cisco Prime Network Registrar

> Unauthenticated remote attackers can cause a partial denial of service by sending malformed DNS packets to Cisco Prime Network Registrar.

- **Severity:** Medium 5.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/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:** 20 Apr 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-3rvq-jp9x-cxmh

## What is CVE-2017-6613?

CVE-2017-6613 is a medium-severity denial of service vulnerability in Cisco Prime Network Registrar, published on 20 Apr 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in the DNS input packet processor for Cisco Prime Network Registrar could allow an unauthenticated, remote attacker to cause the DNS process to momentarily restart, which could lead to a partial denial of service (DoS) condition on the affected system. The vulnerability is due to incomplete DNS packet header validation when the packet is received by the application. An attacker could exploit this vulnerability by sending a malformed DNS packet to the application. An exploit could allow the attacker to cause the DNS process to restart, which could lead to a DoS condition. This vulnerability affects Cisco Prime Network Registrar on all software versions prior to 8.3.5. Cisco Bug IDs: CSCvb55412.

Weakness: CWE-20 (Improper Input Validation), CWE-399

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

It affects 1 product.


Products: Cisco Prime Network Registrar.

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

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

## Is CVE-2017-6613 being exploited?

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

## Other vulnerabilities in Cisco Prime Network Registrar

- [CVE-2019-1840](https://insights.sbomify.com/CVE-2019-1840/): Cisco Prime Network Registrar Denial of Service Vulnerability (high 8.6)
- [CVE-2020-3272](https://insights.sbomify.com/CVE-2020-3272/): Cisco Prime Network Registrar DHCP Denial of Service Vulnerability (high 7.5)
- [CVE-2016-1427](https://insights.sbomify.com/CVE-2016-1427/): Information disclosure in n/a (high 7.5)
- [CVE-2015-6296](https://insights.sbomify.com/CVE-2015-6296/): Hardcoded credentials in n/a (high 7.2)
- [CVE-2020-3148](https://insights.sbomify.com/CVE-2020-3148/): Cisco Prime Network Registrar Cross-Site Request Forgery Vulnerability (high 7.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-6613 is a medium-severity denial of service vulnerability in Cisco Prime Network Registrar, 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-6613 in the wild and no public exploit code.

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

## Sources

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

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