CVE-2024-38321

5.3 MEDIUM

📋 TL;DR

IBM Business Automation Workflow versions 22.0.2 through 24.0.0 store sensitive information in log files that authenticated users can read. This information disclosure vulnerability could expose credentials, configuration details, or other sensitive data. Only authenticated users with access to log files are affected.

💻 Affected Systems

Products:
  • IBM Business Automation Workflow
Versions: 22.0.2, 23.0.1, 23.0.2, 24.0.0
Operating Systems: All supported platforms
Default Config Vulnerable: ⚠️ Yes
Notes: Vulnerability occurs under certain unspecified situations where sensitive information is written to logs. All default installations of affected versions are vulnerable.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

An authenticated attacker reads sensitive credentials or configuration data from logs, leading to privilege escalation, lateral movement, or complete system compromise.

🟠

Likely Case

An authenticated user accidentally discovers or intentionally accesses sensitive operational data like database connection strings, API keys, or user information stored in logs.

🟢

If Mitigated

Log files are properly secured with restricted permissions, and sensitive data is redacted or encrypted, limiting exposure to authorized administrators only.

🌐 Internet-Facing: MEDIUM
🏢 Internal Only: HIGH

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: LOW

Exploitation requires authenticated access to log files. No public exploit code is known, but the attack is straightforward once log access is obtained.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Apply interim fix or upgrade to versions beyond those listed

Vendor Advisory: https://www.ibm.com/support/pages/node/7162334

Restart Required: Yes

Instructions:

1. Review IBM advisory for specific interim fixes. 2. Apply the recommended fix for your version. 3. Restart IBM Business Automation Workflow services. 4. Verify logs no longer contain sensitive information.

🔧 Temporary Workarounds

Restrict log file permissions

linux

Set strict file permissions on log directories to prevent unauthorized read access

chmod 600 /path/to/logs/*.log
chown root:root /path/to/logs/*.log

Configure log redaction

all

Configure logging to redact or mask sensitive information before writing to files

🧯 If You Can't Patch

  • Implement strict access controls on log directories (minimum privilege principle)
  • Regularly audit and monitor log file access for suspicious activity

🔍 How to Verify

Check if Vulnerable:

Check if running affected IBM Business Automation Workflow version and review log files for sensitive data like passwords, tokens, or configuration details

Check Version:

Check IBM Business Automation Workflow administration console or installation documentation for version information

Verify Fix Applied:

After applying fix, verify logs no longer contain sensitive information and check version is updated

📡 Detection & Monitoring

Log Indicators:

  • Unauthorized access attempts to log files
  • Log entries containing sensitive data patterns

Network Indicators:

  • Unusual file access patterns to log directories

SIEM Query:

source="*log*" AND (event="access" OR event="read") AND user!="authorized_admin"

🔗 References

📤 Share & Export