# CVE-2017-1795: Information disclosure in WebSphere MQ

> A local user can obtain highly sensitive information from trace logs in IBM WebSphere MQ Managed File Transfer.

- **Severity:** Medium 4.4 (`CVSS:3.0/A:N/AC:L/AV:L/C:H/I:N/PR:H/S:U/UI:N/E:U/RC:C/RL:O`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Jul 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-3hmq-7955-4976

## What is CVE-2017-1795?

CVE-2017-1795 is a medium-severity vulnerability in IBM WebSphere MQ, published on 6 Jul 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

IBM WebSphere MQ 7.5, 8.0, and 9.0 through 9.0.4 could allow a local user to obtain highly sensitive information via trace logs in IBM WebSphere MQ Managed File Transfer. IBM X-Force ID: 137042.

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

## Which versions are affected by CVE-2017-1795?

It affects 1 product.


Products: Ibm Websphere Mq Managed File Transfer.

## How do I fix CVE-2017-1795?

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

## Is CVE-2017-1795 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-1795 and fix it if it is affected.

What it is: CVE-2017-1795 is a medium-severity vulnerability in IBM WebSphere MQ, published on 6 Jul 2018. 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-2017-1795 in the wild and no public exploit code.

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

## Sources

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

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