CVE-2025-36143

4.7 MEDIUM

📋 TL;DR

CVE-2025-36143 is an OS command injection vulnerability in IBM Lakehouse (watsonx.data 2.2) that allows authenticated privileged users to execute arbitrary commands on the underlying system. This occurs due to improper input validation when processing user-supplied data. Only authenticated users with elevated privileges in affected IBM watsonx.data 2.2 deployments are at risk.

💻 Affected Systems

Products:
  • IBM Lakehouse
  • IBM watsonx.data
Versions: 2.2
Operating Systems: All platforms running IBM watsonx.data 2.2
Default Config Vulnerable: ⚠️ Yes
Notes: Requires authenticated privileged user access; not exploitable by unauthenticated users or standard users.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

An authenticated privileged attacker gains full remote code execution on the host system, potentially leading to complete system compromise, data exfiltration, lateral movement, and persistent backdoor installation.

🟠

Likely Case

Privileged insiders or compromised accounts execute limited commands to escalate privileges, access sensitive data, or disrupt services within the watsonx.data environment.

🟢

If Mitigated

With proper access controls and input validation, the attack surface is reduced to authorized users only, limiting potential damage to their existing privilege scope.

🌐 Internet-Facing: MEDIUM
🏢 Internal Only: HIGH

🎯 Exploit Status

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

Exploitation requires authenticated privileged access and knowledge of vulnerable input vectors; no public exploit code is currently available.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Apply the fix as described in IBM Security Bulletin

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

Restart Required: No

Instructions:

1. Review IBM Security Bulletin for specific patching instructions. 2. Apply the recommended fix or update to a patched version. 3. Verify the fix by testing input validation in affected components.

🔧 Temporary Workarounds

Restrict Privileged Access

all

Limit the number of users with privileged access to watsonx.data to reduce attack surface.

Implement Input Validation

all

Add additional input validation layers for user-supplied data before processing.

🧯 If You Can't Patch

  • Implement strict least-privilege access controls for all watsonx.data users.
  • Monitor and audit privileged user activities for suspicious command execution patterns.

🔍 How to Verify

Check if Vulnerable:

Check if running IBM watsonx.data version 2.2 and review user privilege assignments.

Check Version:

Consult IBM documentation for version checking commands specific to your deployment.

Verify Fix Applied:

Verify the fix by testing previously vulnerable input vectors and confirming proper input validation.

📡 Detection & Monitoring

Log Indicators:

  • Unusual command execution patterns by privileged users
  • Failed input validation attempts in application logs
  • Unexpected system process creation from watsonx.data

Network Indicators:

  • Outbound connections from watsonx.data to unexpected destinations
  • Unusual network traffic patterns following user interactions

SIEM Query:

source="watsonx.data" AND (event_type="command_execution" OR user_privilege="elevated") AND command="*"

🔗 References

📤 Share & Export