CVE-2025-36356

9.3 CRITICAL

📋 TL;DR

This vulnerability allows a locally authenticated user on affected IBM Security Verify Access systems to escalate their privileges to root due to improper privilege management. The flaw exists because the software executes with more privileges than required, enabling privilege escalation attacks. Organizations running IBM Security Verify Access or IBM Security Verify Access Docker versions 10.0.0.0 through 10.0.9.0 or 11.0.0.0 through 11.0.1.0 are affected.

💻 Affected Systems

Products:
  • IBM Security Verify Access
  • IBM Security Verify Access Docker
Versions: 10.0.0.0 through 10.0.9.0 and 11.0.0.0 through 11.0.1.0
Operating Systems: Linux (Docker deployments), Various (appliance deployments)
Default Config Vulnerable: ⚠️ Yes
Notes: Affects both appliance and Docker container deployments. Requires local authenticated access to exploit.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

An attacker with local access gains full root privileges, enabling complete system compromise, data theft, installation of persistent backdoors, and lateral movement to other systems.

🟠

Likely Case

Malicious insider or compromised user account escalates to root, gaining unauthorized access to sensitive security configurations and potentially compromising the entire authentication infrastructure.

🟢

If Mitigated

With proper access controls, network segmentation, and least privilege principles, impact is limited to the specific affected system rather than the entire environment.

🌐 Internet-Facing: LOW
🏢 Internal Only: HIGH

🎯 Exploit Status

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

Exploitation requires local authenticated access. The high CVSS score (9.3) suggests relatively straightforward exploitation once an attacker gains local access.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Apply IBM Security Verify Access 10.0.10.0 or 11.0.2.0 or later

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

Restart Required: Yes

Instructions:

1. Review IBM advisory at the provided URL
2. Download and apply IBM Security Verify Access 10.0.10.0 or 11.0.2.0 or later
3. Restart affected services or systems
4. Verify the update was successful

🔧 Temporary Workarounds

Restrict Local Access

linux

Limit local access to affected systems to only authorized administrators using strict access controls.

# Implement strict sudo/privilege management
# Use mandatory access controls like SELinux/AppArmor

Network Segmentation

all

Isolate affected systems in restricted network segments to limit lateral movement potential.

# Configure firewall rules to restrict access
# Implement network segmentation policies

🧯 If You Can't Patch

  • Implement strict least privilege access controls for all local user accounts
  • Monitor for privilege escalation attempts using security logging and auditing tools

🔍 How to Verify

Check if Vulnerable:

Check the installed version of IBM Security Verify Access. If version is between 10.0.0.0-10.0.9.0 or 11.0.0.0-11.0.1.0, the system is vulnerable.

Check Version:

# For appliance: Check admin console or product documentation
# For Docker: docker inspect <container_name> | grep -i version

Verify Fix Applied:

Verify the installed version is 10.0.10.0 or later for version 10.x, or 11.0.2.0 or later for version 11.x.

📡 Detection & Monitoring

Log Indicators:

  • Unexpected privilege escalation events
  • Root access from non-admin users
  • Failed privilege escalation attempts
  • Unusual process execution with elevated privileges

Network Indicators:

  • Unusual outbound connections from affected systems
  • Lateral movement attempts to other systems

SIEM Query:

source="*verify_access*" AND (event_type="privilege_escalation" OR user="root" AND source_user!="admin")

🔗 References

📤 Share & Export