CVE-2025-13148

8.1 HIGH

📋 TL;DR

This vulnerability in IBM Aspera Orchestrator allows authenticated users to change other users' passwords without knowing their current passwords. This affects all installations of IBM Aspera Orchestrator versions 4.0.0 through 4.1.0. The flaw enables privilege escalation and account takeover within the application.

💻 Affected Systems

Products:
  • IBM Aspera Orchestrator
Versions: 4.0.0 through 4.1.0
Operating Systems: All supported platforms
Default Config Vulnerable: ⚠️ Yes
Notes: All deployments within the affected version range are vulnerable regardless of configuration.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

An attacker with any authenticated account could change administrator passwords, gain full system control, and potentially pivot to other systems.

🟠

Likely Case

Malicious insider or compromised low-privilege account escalates privileges to administrative access, leading to data theft or system manipulation.

🟢

If Mitigated

With proper access controls and monitoring, impact is limited to unauthorized password changes that can be detected and reversed.

🌐 Internet-Facing: MEDIUM
🏢 Internal Only: HIGH

🎯 Exploit Status

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

Exploitation requires authenticated access but is straightforward once authenticated.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 4.1.1 and later

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

Restart Required: Yes

Instructions:

1. Download IBM Aspera Orchestrator 4.1.1 or later from IBM Fix Central. 2. Follow IBM's upgrade documentation for your deployment type. 3. Restart all Orchestrator services after installation.

🔧 Temporary Workarounds

Restrict User Permissions

all

Review and minimize user permissions to limit who can access user management functions.

Enhanced Monitoring

all

Implement strict monitoring of user account changes and password reset activities.

🧯 If You Can't Patch

  • Implement strict access controls and principle of least privilege for all user accounts.
  • Enable detailed auditing of all user management activities and review logs daily.

🔍 How to Verify

Check if Vulnerable:

Check the Aspera Orchestrator version in the web interface under Admin > About or via the installation directory.

Check Version:

Check web interface or installation documentation for version information.

Verify Fix Applied:

Verify version is 4.1.1 or later and test that authenticated users cannot change other users' passwords without proper authorization.

📡 Detection & Monitoring

Log Indicators:

  • Unexpected password change events
  • User account modifications by non-admin users
  • Failed authentication attempts followed by password resets

Network Indicators:

  • HTTP POST requests to user management endpoints from unexpected sources

SIEM Query:

source="aspera_orchestrator" AND (event_type="password_change" OR event_type="user_modify")

🔗 References

📤 Share & Export