CVE-2024-54173
📋 TL;DR
IBM MQ versions 9.3 and 9.4 expose sensitive information in trace files when webconsole trace is enabled. This information disclosure vulnerability allows local users to read potentially sensitive data from these files. Only systems with webconsole trace enabled are affected.
💻 Affected Systems
- IBM MQ
📦 What is this software?
⚠️ Risk & Real-World Impact
Worst Case
Local attackers could extract credentials, configuration secrets, or other sensitive data from trace files, potentially enabling further system compromise.
Likely Case
Local users with access to trace files could read configuration details or other non-critical sensitive information.
If Mitigated
With proper access controls and trace disabled, the vulnerability has minimal impact.
🎯 Exploit Status
Exploitation requires local access to the system and read access to trace files. No authentication bypass needed beyond local file access.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: Apply interim fix or upgrade to fixed versions as specified in IBM advisory
Vendor Advisory: https://www.ibm.com/support/pages/node/7183370
Restart Required: Yes
Instructions:
1. Review IBM advisory for specific fix versions. 2. Apply interim fix or upgrade to patched version. 3. Restart IBM MQ services. 4. Verify trace functionality if needed.
🔧 Temporary Workarounds
Disable webconsole trace
allTurn off webconsole trace functionality to prevent sensitive information from being written to trace files
mqsc -n -s QMGR_NAME
ALTER QMGR TRACE(CONSOLE=OFF)
Restrict trace file permissions
linuxSet strict file permissions on trace directories to prevent unauthorized local access
chmod 700 /var/mqm/trace/
chown mqm:mqm /var/mqm/trace/
🧯 If You Can't Patch
- Disable webconsole trace functionality immediately
- Implement strict file system permissions on trace directories and monitor access
🔍 How to Verify
Check if Vulnerable:
Check if webconsole trace is enabled using 'dspmqtrc' command or examine MQ configuration
Check Version:
dspmqver
Verify Fix Applied:
Verify trace files no longer contain sensitive information and check applied fix version
📡 Detection & Monitoring
Log Indicators:
- Unauthorized access attempts to trace file directories
- Trace files containing unexpected sensitive data
Network Indicators:
- N/A - local file access only
SIEM Query:
EventID=4663 AND ObjectName LIKE '%trace%' AND AccessMask=0x1