# CVE-2020-4592: IBM MQ Appliance 9.1.CD and LTS could allow an authenticated user, under nondefault configuration to cause a data corruption attack due to a


- **Severity:** Medium 5.3 (`CVSS:3.0/PR:L/AV:N/AC:H/S:U/UI:N/I:H/C:N/A:N/RL:O/RC:C/E:U`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 18 Nov 2020
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-w986-fvg4-hvqg

## What is CVE-2020-4592?

CVE-2020-4592 is a medium-severity vulnerability in IBM MQ Appliance, published on 18 Nov 2020. 

### Official description

IBM MQ Appliance 9.1.CD and LTS could allow an authenticated user, under nondefault configuration to cause a data corruption attack due to an error when using segmented messages.

## Which versions are affected by CVE-2020-4592?

It affects 1 product.


Products: Ibm Mq Appliance.

## How do I fix CVE-2020-4592?

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

## Is CVE-2020-4592 being exploited?

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

## Other vulnerabilities in IBM MQ Appliance

- [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-2020-4592 and fix it if it is affected.

What it is: CVE-2020-4592 is a medium-severity vulnerability in IBM MQ Appliance, published on 18 Nov 2020. 
Exploitation: There is no known exploitation of CVE-2020-4592 in the wild and no public exploit code.

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

## Sources

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

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