CVE-2024-12755

7.9 HIGH

📋 TL;DR

A Cross-Site Scripting (XSS) vulnerability in Avaya Spaces allows attackers to inject malicious scripts into web pages viewed by other users. This could lead to session hijacking, data theft, or unauthorized actions performed on behalf of victims. Organizations using vulnerable versions of Avaya Spaces are affected.

💻 Affected Systems

Products:
  • Avaya Spaces
Versions: Specific versions not detailed in advisory; check Avaya documentation for affected releases
Operating Systems: Not OS-specific; web-based application
Default Config Vulnerable: ⚠️ Yes
Notes: Vulnerability exists in the web interface of Avaya Spaces; all deployments with affected versions are vulnerable unless patched.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could steal session cookies, credentials, or sensitive data from users, perform unauthorized actions in their accounts, or redirect users to malicious sites.

🟠

Likely Case

Attackers would typically steal session cookies to hijack user accounts, potentially accessing sensitive conversations, files, or contact information within Avaya Spaces.

🟢

If Mitigated

With proper input validation and output encoding, the vulnerability would be prevented, and even if exploited, additional security controls like Content Security Policy (CSP) could limit damage.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Exploitation typically requires tricking a user into interacting with malicious content; no public exploit code is known at this time.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Check Avaya advisory for specific patched versions

Vendor Advisory: https://support.avaya.com/css/public/documents/101091836

Restart Required: No

Instructions:

1. Review Avaya advisory for affected versions. 2. Apply the recommended patch or update to a fixed version. 3. Verify the fix by testing the application.

🔧 Temporary Workarounds

Implement Content Security Policy (CSP)

all

Deploy a strict CSP to mitigate XSS by restricting sources of executable scripts.

Add CSP headers in web server configuration, e.g., Content-Security-Policy: default-src 'self'; script-src 'self'

🧯 If You Can't Patch

  • Isolate Avaya Spaces deployment behind a web application firewall (WAF) with XSS protection rules.
  • Educate users to avoid clicking suspicious links and enable browser security features like script blockers.

🔍 How to Verify

Check if Vulnerable:

Check Avaya Spaces version against the advisory; test for XSS by attempting to inject scripts in user-input fields.

Check Version:

Check Avaya Spaces admin interface or documentation for version information; no universal CLI command available.

Verify Fix Applied:

After patching, retest XSS vectors to ensure scripts are properly sanitized and do not execute.

📡 Detection & Monitoring

Log Indicators:

  • Unusual script tags or JavaScript in HTTP requests
  • Multiple failed login attempts from unexpected locations after XSS

Network Indicators:

  • HTTP requests containing suspicious script payloads to Avaya Spaces endpoints

SIEM Query:

source="avaya_spaces" AND (http_request LIKE "%<script>%" OR http_request LIKE "%javascript:%")

🔗 References

📤 Share & Export