CVE-2025-23227

6.4 MEDIUM

📋 TL;DR

IBM Tivoli Application Dependency Discovery Manager versions 7.3.0.0 through 7.3.0.11 contain a stored cross-site scripting (XSS) vulnerability that allows authenticated users to inject malicious JavaScript into the web interface. This could enable attackers to steal credentials or perform unauthorized actions within authenticated sessions. Only authenticated users can exploit this vulnerability.

💻 Affected Systems

Products:
  • IBM Tivoli Application Dependency Discovery Manager
Versions: 7.3.0.0 through 7.3.0.11
Operating Systems: All supported platforms
Default Config Vulnerable: ⚠️ Yes
Notes: Requires authenticated access to the web interface; all default configurations are vulnerable.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

An authenticated malicious insider or compromised account could inject JavaScript that captures administrator credentials, leading to full system compromise and data exfiltration.

🟠

Likely Case

Authenticated attackers could perform session hijacking, redirect users to malicious sites, or deface the web interface.

🟢

If Mitigated

With proper input validation and output encoding, the risk is limited to minor UI manipulation with no data compromise.

🌐 Internet-Facing: MEDIUM
🏢 Internal Only: HIGH

🎯 Exploit Status

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

Exploitation requires authenticated access; stored XSS typically has low technical complexity once access is obtained.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 7.3.0.12 or later

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

Restart Required: Yes

Instructions:

1. Download IBM Tivoli Application Dependency Discovery Manager 7.3.0.12 or later from IBM Fix Central. 2. Backup current installation. 3. Apply the update following IBM's installation guide. 4. Restart the application server.

🔧 Temporary Workarounds

Input Validation Filter

all

Implement server-side input validation to sanitize user inputs before storage.

Custom implementation required - no standard commands

Content Security Policy

all

Implement CSP headers to restrict execution of inline JavaScript.

Add 'Content-Security-Policy: script-src 'self'' to web server configuration

🧯 If You Can't Patch

  • Restrict user permissions to minimize authenticated users who could exploit the vulnerability
  • Implement web application firewall (WAF) rules to detect and block XSS payloads

🔍 How to Verify

Check if Vulnerable:

Check the installed version via the web interface admin panel or by examining installation files.

Check Version:

Check the version in the web interface under Help > About or examine the product installation directory for version files.

Verify Fix Applied:

Verify version is 7.3.0.12 or later and test XSS payloads in user input fields to confirm sanitization.

📡 Detection & Monitoring

Log Indicators:

  • Unusual JavaScript patterns in user input fields
  • Multiple failed XSS attempts in web logs

Network Indicators:

  • Suspicious JavaScript payloads in HTTP POST requests to the application

SIEM Query:

source="web_logs" AND (url="*/taddm/*" OR app="IBM TADDM") AND (message="*<script>*" OR message="*javascript:*")

🔗 References

📤 Share & Export