# CVE-2019-4619: Information disclosure in MQ

> A local attacker can obtain sensitive information from trace logs in IBM MQ, requiring trace features to be enabled.

- **Severity:** Medium 5.1 (`CVSS:3.0/PR:N/AV:L/AC:H/A:N/I:N/UI:N/S:U/C:H/RL:O/RC:C/E:U`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Mar 2020
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-9q3c-fv37-7prc

## What is CVE-2019-4619?

CVE-2019-4619 is a medium-severity vulnerability in Ibm Mq, published on 16 Mar 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

IBM MQ and IBM MQ Appliance 7.1, 7.5, 8.0, 9.0 LTS, 9.1 LTS, and 9.1 CD could allow a local attacker to obtain sensitive information by inclusion of sensitive data within trace. IBM X-Force ID: 168862.

Weakness: CWE-209 (Generation of Error Message Containing Sensitive Information)

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

It affects 3 products.


Products: Ibm Mq, Ibm Mq Appliance, Ibm Websphere Mq.

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

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

## Is CVE-2019-4619 being exploited?

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

## Other vulnerabilities in Ibm Mq

- [CVE-2026-10575](https://insights.sbomify.com/CVE-2026-10575/): IBM MQ queue manager is vulnerable to remote code execution (high 8.8)
- [CVE-2026-11375](https://insights.sbomify.com/CVE-2026-11375/): IBM MQ queue manager is vulnerable to remote code execution (high 8.8)
- [CVE-2026-11378](https://insights.sbomify.com/CVE-2026-11378/): IBM MQ queue manager is vulnerable to remote code execution (high 8.8)
- [CVE-2022-22489](https://insights.sbomify.com/CVE-2022-22489/): XML external entity in MQ (high 8.2)
- [CVE-2026-10027](https://insights.sbomify.com/CVE-2026-10027/): IBM MQ queue manager is vulnerable to unauthenticated remote code execution (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-4619 is a medium-severity vulnerability in Ibm Mq, published on 16 Mar 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-4619 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-4619/ (Markdown: https://insights.sbomify.com/CVE-2019-4619/index.md)
```

## Sources

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

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