# CVE-2022-35719: Information disclosure in MQ Internet Pass-Thru

> Local users can read sensitive information from trace files in IBM MQ Internet Pass-Thru, requiring a patch to mitigate data exposure.

- **Severity:** Medium 5.1 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **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:** 14 Nov 2022
- **Updated:** 25 Apr 2025
- **Also known as:** GHSA-w2mg-q8wx-4hqp

## What is CVE-2022-35719?

CVE-2022-35719 is a medium-severity vulnerability in IBM MQ Internet Pass-Thru, published on 14 Nov 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

IBM MQ Internet Pass-Thru 2.1, 9.2 LTS and 9.2 CD stores potentially sensitive information in trace files that could be read by a local user.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2022-35719?

It affects 1 product.


Products: Ibm Mq Internet Pass-Thru.

## How do I fix CVE-2022-35719?

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

## Is CVE-2022-35719 being exploited?

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

## Other vulnerabilities in IBM MQ Internet Pass-Thru

- [CVE-2020-4766](https://insights.sbomify.com/CVE-2020-4766/): Denial of service in MQ Internet Pass-Thru (medium 5.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-35719 and fix it if it is affected.

What it is: CVE-2022-35719 is a medium-severity vulnerability in IBM MQ Internet Pass-Thru, published on 14 Nov 2022. 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-2022-35719 in the wild and no public exploit code.

Affected product: IBM MQ Internet Pass-Thru. 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-2022-35719/ (Markdown: https://insights.sbomify.com/CVE-2022-35719/index.md)
```

## Sources

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

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