IBM MQ 9.1.4 could allow a local attacker to obtain sensitive information by inclusion of sensitive data within runmqras data.

published 2020-04-16 6y ago modified 2026-06-17 4mo ago also EUVD-2020-25585

cvss: 5.1; version 3.0, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.3%; EPSS 0.3% chance of exploitation in 30 days, percentile 26%
public exploits: 0; none known

IBM MQ 9.1.4 could allow a local attacker to obtain sensitive information by inclusion of sensitive data within runmqras data. IBM X-Force ID: 177937.

Patch / fix

fixed in 1

ibm mq 9.1.5

Is CVE-2020-4338 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.33% chance of exploitation in the next 30 days, higher than 26% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
CNA	3.0	5.1	CVSS:3.0/UI:N/PR:N/A:N/I:N/AC:H/AV:L/C:H/S:U/RC:C/E:U/RL:O
NVD	3.1	5.5	CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
CNA	3.0	5.1	CVSS:3.0/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
NVD	2.0	2.1	AV:L/AC:L/Au:N/C:P/I:N/A:N

Affected products

IBM MQ

Classification

Weakness

CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

ibm.com /support/pages/node/6172539
vendor-advisory
exchange.xforce.ibmcloud.com /vulnerabilities/177937
vdb-entry, vendor-advisory

Sources

CVE List CVE-2020-4338
NVD CVE-2020-4338

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.