CVE-2024-36156

5.4 MEDIUM

📋 TL;DR

This stored XSS vulnerability in Adobe Experience Manager allows attackers to inject malicious JavaScript into vulnerable form fields. When users visit pages containing these compromised fields, their browsers execute the attacker's code. This affects all Adobe Experience Manager versions 6.5.20 and earlier.

💻 Affected Systems

Products:
  • Adobe Experience Manager
Versions: 6.5.20 and earlier
Operating Systems: All platforms running Adobe Experience Manager
Default Config Vulnerable: ⚠️ Yes
Notes: All installations of affected versions are vulnerable regardless of configuration.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could steal administrator credentials, hijack user sessions, deface websites, or redirect users to malicious sites, potentially leading to complete system compromise.

🟠

Likely Case

Attackers inject malicious scripts to steal user session cookies or credentials, enabling unauthorized access to the AEM system and potentially other connected systems.

🟢

If Mitigated

With proper input validation and output encoding, the vulnerability would be prevented, though the underlying code flaw would still exist.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Exploitation requires access to vulnerable form fields, which typically requires some level of authenticated access.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 6.5.21 or later

Vendor Advisory: https://helpx.adobe.com/security/products/experience-manager/apsb24-28.html

Restart Required: Yes

Instructions:

1. Download Adobe Experience Manager 6.5.21 or later from Adobe's distribution portal. 2. Apply the service pack following Adobe's upgrade documentation. 3. Restart the AEM instance. 4. Verify the update was successful.

🔧 Temporary Workarounds

Input Validation Filter

all

Implement custom servlet filters to sanitize all user input before processing.

Implement custom Java servlet filter with input validation logic

Content Security Policy

all

Implement strict Content Security Policy headers to prevent script execution from untrusted sources.

Add 'Content-Security-Policy' header with script-src directives

🧯 If You Can't Patch

  • Implement web application firewall (WAF) rules to block XSS payloads
  • Disable or restrict access to vulnerable form fields and components

🔍 How to Verify

Check if Vulnerable:

Check AEM version via the welcome page or system console. Versions 6.5.20 and earlier are vulnerable.

Check Version:

Navigate to /system/console/status-productinfo in AEM or check the welcome page

Verify Fix Applied:

Verify AEM version is 6.5.21 or later and test form fields with XSS payloads to ensure they're properly sanitized.

📡 Detection & Monitoring

Log Indicators:

  • Unusual content submissions containing script tags or JavaScript code
  • Multiple failed XSS attempts in request logs

Network Indicators:

  • HTTP requests containing suspicious script payloads in form parameters

SIEM Query:

source="aem_logs" AND ("<script>" OR "javascript:" OR "onerror=" OR "onload=")

🔗 References

📤 Share & Export