# CVE-2015-0224: Denial of service in n/a

> Remote attackers can crash the Apache Qpid broker daemon by sending a crafted protocol sequence, resulting in a denial of service.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/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:** Yes
- **Published:** 30 Oct 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-qrxf-m4mx-cp67

## What is CVE-2015-0224?

CVE-2015-0224 is a high-severity denial of service vulnerability in n/a, published on 30 Oct 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

qpidd in Apache Qpid 0.30 and earlier allows remote attackers to cause a denial of service (daemon crash) via a crafted protocol sequence set.  NOTE: this vulnerability exists because of an incomplete fix for CVE-2015-0203.

Weakness: CWE-19

## Which versions are affected by CVE-2015-0224?

It affects 1 product.


Products: Apache Qpid.

## How do I fix CVE-2015-0224?

Apply the vendor's patch.

## Is CVE-2015-0224 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2011-3620](https://insights.sbomify.com/CVE-2011-3620/): Auth bypass in n/a (high 7.5)
- [CVE-2019-0223](https://insights.sbomify.com/CVE-2019-0223/): Security feature bypass in Apache Qpid Proton (high 7.4)
- [CVE-2012-4446](https://insights.sbomify.com/CVE-2012-4446/): Improper Authentication in Apache Qpid (medium 6.8)
- [CVE-2015-0203](https://insights.sbomify.com/CVE-2015-0203/): Denial of service in n/a (medium 6.5)
- [CVE-2013-1909](https://insights.sbomify.com/CVE-2013-1909/): Apache Qpid Python client Improper certificate validation (medium 5.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-0224 and fix it if it is affected.

What it is: CVE-2015-0224 is a high-severity denial of service vulnerability in n/a, published on 30 Oct 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-2015-0224 in the wild and no public exploit code.

Affected product: n/a. 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-2015-0224/ (Markdown: https://insights.sbomify.com/CVE-2015-0224/index.md)
```

## Sources

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

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