CVE-2024-25029

9.0 CRITICAL

📋 TL;DR

This vulnerability in IBM Personal Communications allows any unprivileged user with network access to execute arbitrary commands with SYSTEM privileges. It enables both remote code execution and local privilege escalation, affecting organizations using vulnerable versions of this software.

💻 Affected Systems

Products:
  • IBM Personal Communications
Versions: 14.0.6 through 15.0.1
Operating Systems: Windows
Default Config Vulnerable: ⚠️ Yes
Notes: Affects the Windows service component of IBM Personal Communications. All installations within the vulnerable version range are affected.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Full system compromise allowing attackers to execute arbitrary code as SYSTEM, move laterally across the network, and establish persistent access.

🟠

Likely Case

Internal attackers or compromised low-privilege accounts escalating to SYSTEM privileges and moving laterally to other systems.

🟢

If Mitigated

Limited impact if network segmentation restricts access to vulnerable systems and proper privilege separation is in place.

🌐 Internet-Facing: HIGH if vulnerable service is exposed to internet, as unauthenticated attackers can achieve full system compromise.
🏢 Internal Only: HIGH as any internal user with network access can exploit this to gain SYSTEM privileges.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

The vulnerability allows unauthenticated remote exploitation with low complexity, making it highly dangerous if exposed.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 15.0.2 and later

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

Restart Required: Yes

Instructions:

1. Download IBM Personal Communications version 15.0.2 or later from IBM support. 2. Install the update following IBM's installation guide. 3. Restart the system to ensure the vulnerable service is replaced.

🔧 Temporary Workarounds

Network Access Restriction

windows

Restrict network access to the vulnerable service using firewall rules

netsh advfirewall firewall add rule name="Block IBM PC Service" dir=in action=block protocol=TCP localport=[PORT_NUMBER]

Service Disablement

windows

Temporarily disable the vulnerable Windows service if not required

sc stop "IBM Personal Communications Service"
sc config "IBM Personal Communications Service" start= disabled

🧯 If You Can't Patch

  • Implement strict network segmentation to isolate vulnerable systems from general network access
  • Apply principle of least privilege and monitor for unusual SYSTEM privilege usage

🔍 How to Verify

Check if Vulnerable:

Check IBM Personal Communications version via Control Panel > Programs and Features, or run: wmic product where "name like 'IBM Personal Communications%'" get version

Check Version:

wmic product where "name like 'IBM Personal Communications%'" get version

Verify Fix Applied:

Verify installed version is 15.0.2 or later using the same version check command

📡 Detection & Monitoring

Log Indicators:

  • Windows Event Logs showing unexpected service starts/stops
  • Security logs showing privilege escalation to SYSTEM
  • Application logs showing unusual IBM Personal Communications service activity

Network Indicators:

  • Unexpected network connections to IBM Personal Communications service port
  • Network traffic patterns indicating lateral movement from vulnerable systems

SIEM Query:

source="Windows Security" EventCode=4688 NewProcessName="*SYSTEM*" | where ProcessName contains "IBM Personal Communications"

🔗 References

📤 Share & Export