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

> Remote attackers can crash the IBM MessageSight server and cause data loss by sending malformed headers during WebSocket connections.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Apr 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-4w2f-r3pq-3wfp

## What is CVE-2014-0921?

CVE-2014-0921 is a medium-severity denial of service vulnerability in n/a, published on 15 Apr 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The server in IBM MessageSight 1.x before 1.1.0.0-IBM-IMA-IT01015 allows remote attackers to cause a denial of service (daemon crash and message data loss) via malformed headers during a WebSockets connection upgrade.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 2 products.


Products: Ibm Messagesight, Ibm Messagesight Jms Client.

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

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

## Is CVE-2014-0921 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-0375](https://insights.sbomify.com/CVE-2016-0375/): Privilege escalation in n/a (high 8.8)
- [CVE-2014-0924](https://insights.sbomify.com/CVE-2014-0924/): Auth bypass in n/a (medium 4.6)
- [CVE-2014-0922](https://insights.sbomify.com/CVE-2014-0922/): Denial of service in n/a (medium 4.3)
- [CVE-2014-0923](https://insights.sbomify.com/CVE-2014-0923/): Denial of service in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-0921 is a medium-severity denial of service vulnerability in n/a, published on 15 Apr 2014. 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-2014-0921 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-0921/ (Markdown: https://insights.sbomify.com/CVE-2014-0921/index.md)
```

## Sources

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

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