# CVE-2017-15699: Denial of service in Apache Qpid Dispatch Router

> Remote attackers can crash the Apache Qpid Dispatch Router by sending a crafted AMQP frame, causing a denial of service.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Feb 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-mf5v-gg97-x6pj

## What is CVE-2017-15699?

CVE-2017-15699 is a medium-severity denial of service vulnerability in Apache Qpid Dispatch Router, published on 13 Feb 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A Denial of Service vulnerability was found in Apache Qpid Dispatch Router versions 0.7.0 and 0.8.0. To exploit this vulnerability, a remote user must be able to establish an AMQP connection to the Qpid Dispatch Router and send a specifically crafted AMQP frame which will cause it to segfault and shut down.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Apache Qpid Dispatch.

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

Upgrade to a fixed version.

## Is CVE-2017-15699 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-15699 is a medium-severity denial of service vulnerability in Apache Qpid Dispatch Router, published on 13 Feb 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-15699 in the wild and no public exploit code.

Affected product: Apache Qpid Dispatch Router. 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-15699/ (Markdown: https://insights.sbomify.com/CVE-2017-15699/index.md)
```

## Sources

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

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