CVE-2024-49807

6.4 MEDIUM

📋 TL;DR

This stored XSS vulnerability in IBM Sterling B2B Integrator allows authenticated users to inject malicious JavaScript into the web interface. If exploited, it could lead to session hijacking or credential theft within trusted sessions. Affected versions include 6.0.0.0 through 6.1.2.5 and 6.2.0.0 through 6.2.0.3.

💻 Affected Systems

Products:
  • IBM Sterling B2B Integrator Standard Edition
Versions: 6.0.0.0 through 6.1.2.5 and 6.2.0.0 through 6.2.0.3
Operating Systems: All supported platforms
Default Config Vulnerable: ⚠️ Yes
Notes: Requires authenticated user access; affects web UI components.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers steal administrator credentials, gain full system control, and compromise sensitive B2B transaction data.

🟠

Likely Case

Authenticated attackers steal session cookies or credentials from other users, leading to unauthorized access.

🟢

If Mitigated

With proper input validation and output encoding, the attack surface is reduced, though authenticated users could still inject content.

🌐 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 complexity once the injection point is identified.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Apply interim fix or upgrade to versions beyond affected ranges

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

Restart Required: Yes

Instructions:

1. Review IBM advisory for specific patch details. 2. Apply the recommended interim fix or upgrade to a non-vulnerable version. 3. Restart the Sterling B2B Integrator service.

🔧 Temporary Workarounds

Input Validation and Output Encoding

all

Implement server-side validation and encoding for user inputs in web UI components.

Content Security Policy (CSP)

all

Deploy a strict CSP to mitigate XSS impact by restricting script execution.

🧯 If You Can't Patch

  • Restrict authenticated user permissions to minimize attack surface.
  • Monitor web application logs for suspicious JavaScript injection attempts.

🔍 How to Verify

Check if Vulnerable:

Check the Sterling B2B Integrator version against affected ranges in the vendor advisory.

Check Version:

Consult IBM documentation for version check commands specific to your deployment.

Verify Fix Applied:

Verify the applied patch version matches or exceeds the fixed versions listed by IBM.

📡 Detection & Monitoring

Log Indicators:

  • Unusual JavaScript payloads in web request logs
  • Multiple failed injection attempts

Network Indicators:

  • Suspicious outbound connections from the Sterling server

SIEM Query:

source="sterling_logs" AND (message="*script*" OR message="*javascript*")

🔗 References

📤 Share & Export