CVE-2024-4190

8.1 HIGH

📋 TL;DR

Stored Cross-Site Scripting (XSS) vulnerabilities in OpenText ArcSight Logger allow attackers to inject malicious scripts that persist in the application and execute when other users view affected pages. This could lead to session hijacking, data theft, or unauthorized actions performed on behalf of legitimate users. Organizations using vulnerable versions of ArcSight Logger are affected.

💻 Affected Systems

Products:
  • OpenText ArcSight Logger
Versions: Specific versions not detailed in advisory; all versions before the fix are likely affected
Operating Systems: All supported platforms
Default Config Vulnerable: ⚠️ Yes
Notes: Vulnerability affects web interface components where user input is stored and later displayed without proper sanitization.

⚠️ Manual Verification Required

This CVE does not have specific version information in our database, so automatic vulnerability detection cannot determine if your system is affected.

Why? The CVE database entry doesn't specify which versions are vulnerable (no version ranges provided by the vendor/NVD).

🔒 Custom verification scripts are available for registered users. Sign up free to download automated test scripts.

Recommended Actions:
  1. Review the CVE details at NVD
  2. Check vendor security advisories for your specific version
  3. Test if the vulnerability is exploitable in your environment
  4. Consider updating to the latest version as a precaution

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could steal administrator credentials, compromise the entire ArcSight Logger instance, pivot to other systems, and maintain persistent access to sensitive security logs and infrastructure.

🟠

Likely Case

Attackers inject malicious JavaScript to steal session cookies, redirect users to phishing sites, or perform unauthorized actions within the ArcSight Logger interface.

🟢

If Mitigated

With proper input validation, output encoding, and Content Security Policy (CSP) headers, the impact is limited to potential UI disruption without data compromise.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Stored XSS typically requires some level of access to input fields, but exploitation is straightforward once access is obtained.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Check vendor advisory for specific patched versions

Vendor Advisory: https://portal.microfocus.com/s/article/KM000030655

Restart Required: Yes

Instructions:

1. Review vendor advisory KM000030655. 2. Download and apply the latest security patch from OpenText. 3. Restart ArcSight Logger services. 4. Verify the patch is applied successfully.

🔧 Temporary Workarounds

Implement Content Security Policy

all

Add CSP headers to restrict script execution sources

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

Input Validation Rules

all

Configure WAF or application firewall to block XSS patterns

Configure WAF rules to detect and block <script>, javascript:, and other XSS patterns

🧯 If You Can't Patch

  • Isolate ArcSight Logger instance from internet access
  • Implement strict access controls and monitor for suspicious input patterns

🔍 How to Verify

Check if Vulnerable:

Check ArcSight Logger version against vendor advisory; test input fields for script injection

Check Version:

Check ArcSight Logger web interface or installation directory for version information

Verify Fix Applied:

Verify patch version is installed and test previously vulnerable input fields

📡 Detection & Monitoring

Log Indicators:

  • Unusual input patterns containing script tags or JavaScript in web logs
  • Multiple failed input validation attempts

Network Indicators:

  • HTTP requests containing suspicious script payloads to ArcSight Logger endpoints

SIEM Query:

source="arcsight_logger" AND (http_uri CONTAINS "<script>" OR http_body CONTAINS "javascript:")

🔗 References

📤 Share & Export