CVE-2025-1411

7.8 HIGH

📋 TL;DR

This vulnerability in IBM Security Verify Directory Container allows local users to execute arbitrary commands with root privileges due to unnecessary privilege escalation. It affects IBM Security Verify Directory Container versions 10.0.0.0 through 10.0.3.1. Attackers with local access can gain complete system control.

💻 Affected Systems

Products:
  • IBM Security Verify Directory Container
Versions: 10.0.0.0 through 10.0.3.1
Operating Systems: Linux (containerized deployment)
Default Config Vulnerable: ⚠️ Yes
Notes: Affects container deployments of IBM Security Verify Directory; requires local user access to the container.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete system compromise with root-level persistence, data exfiltration, lateral movement, and backdoor installation.

🟠

Likely Case

Local privilege escalation leading to credential theft, configuration modification, and service disruption.

🟢

If Mitigated

Limited impact if proper access controls, least privilege principles, and network segmentation are implemented.

🌐 Internet-Facing: LOW - Requires local access to the container, not directly exploitable over network.
🏢 Internal Only: HIGH - Any compromised internal account with local access can escalate to root privileges.

🎯 Exploit Status

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

Exploitation requires local user access but is likely straightforward once access is obtained.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 10.0.3.2 or later

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

Restart Required: Yes

Instructions:

1. Download IBM Security Verify Directory Container version 10.0.3.2 or later from IBM Fix Central. 2. Stop the vulnerable container. 3. Deploy the updated container image. 4. Verify the new version is running correctly.

🔧 Temporary Workarounds

Restrict Local Access

linux

Limit local user access to the container through strict access controls and user management.

# Review and restrict user accounts with container access
# Implement least privilege for all container users

Container Hardening

linux

Apply container security best practices to reduce attack surface.

# Run container with non-root user if possible
# Apply seccomp profiles and AppArmor/SELinux policies
# Limit container capabilities

🧯 If You Can't Patch

  • Implement strict access controls to limit who can access the container locally.
  • Monitor container activity for suspicious privilege escalation attempts and command execution.

🔍 How to Verify

Check if Vulnerable:

Check the IBM Security Verify Directory Container version. If it's between 10.0.0.0 and 10.0.3.1 inclusive, it's vulnerable.

Check Version:

docker exec <container_name> cat /opt/ibm/ldap/VERSION  # or check container image tag

Verify Fix Applied:

Verify the container is running version 10.0.3.2 or later and test that local users cannot execute commands as root.

📡 Detection & Monitoring

Log Indicators:

  • Unexpected privilege escalation events
  • Root command execution from non-root users
  • Container security policy violations

Network Indicators:

  • Unusual outbound connections from container after local access events

SIEM Query:

source="container_logs" AND (event="privilege_escalation" OR user="root" AND process!="expected_root_processes")

🔗 References

📤 Share & Export