# CVE-2019-4560: Denial of service in MQ

> Attackers can cause a denial of service in IBM MQ by sending poorly formatted messages through channels.

- **Severity:** Medium 5.3 (`CVSS:3.0/C:N/AC:H/S:U/UI:N/AV:N/PR:L/A:H/I:N/E:U/RC:C/RL:O`)
- **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:** 16 Dec 2019
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-hc3j-rrgh-fm8r

## What is CVE-2019-4560?

CVE-2019-4560 is a medium-severity denial of service vulnerability in IBM MQ, published on 16 Dec 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

IBM MQ and IBM MQ Appliance 9.1 CD, 9.1 LTS, 9.0 LTS, and 8.0 is vulnerable to a denial of service attack caused by channels processing poorly formatted messages. IBM X-Force ID: 166357.

## Which versions are affected by CVE-2019-4560?

It affects 1 product.


Products: Ibm Mq Appliance.

## How do I fix CVE-2019-4560?

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

## Is CVE-2019-4560 being exploited?

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

## Other vulnerabilities in IBM MQ

- [CVE-2025-0975](https://insights.sbomify.com/CVE-2025-0975/): IBM MQ code execution (high 8.8)
- [CVE-2017-1318](https://insights.sbomify.com/CVE-2017-1318/): Command injection in MQ Appliance (high 8.8)
- [CVE-2019-4620](https://insights.sbomify.com/CVE-2019-4620/): Security feature bypass in MQ Appliance (high 8.4)
- [CVE-2021-38967](https://insights.sbomify.com/CVE-2021-38967/): Code injection in MQ Appliance (high 8.2)
- [CVE-2024-25048](https://insights.sbomify.com/CVE-2024-25048/): IBM MQ code execution (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-4560 and fix it if it is affected.

What it is: CVE-2019-4560 is a medium-severity denial of service vulnerability in IBM MQ, published on 16 Dec 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-4560 in the wild and no public exploit code.

Affected product: IBM MQ. 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-2019-4560/ (Markdown: https://insights.sbomify.com/CVE-2019-4560/index.md)
```

## Sources

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

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