# CVE-2014-2814: Denial of service in n/a

> Remote authenticated users can cause a denial of service in Microsoft Service Bus by sending crafted AMQP messages.

- **Severity:** Medium 4.0 (`AV:N/AC:L/Au:S/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jul 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-9fcv-hvgf-49wh

## What is CVE-2014-2814?

CVE-2014-2814 is a medium-severity denial of service vulnerability in n/a, published on 8 Jul 2014. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Microsoft Service Bus 1.1 on Microsoft Windows Server 2008 R2 SP1 and Server 2012 Gold and R2 allows remote authenticated users to cause a denial of service (AMQP messaging outage) via crafted AMQP messages, aka "Service Bus Denial of Service Vulnerability."

## Which versions are affected by CVE-2014-2814?

It affects 1 product.


Products: Microsoft Service Bus.

## How do I fix CVE-2014-2814?

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

## Is CVE-2014-2814 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-2814 and fix it if it is affected.

What it is: CVE-2014-2814 is a medium-severity denial of service vulnerability in n/a, published on 8 Jul 2014. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-2814 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-2014-2814/ (Markdown: https://insights.sbomify.com/CVE-2014-2814/index.md)
```

## Sources

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

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