CVE-2024-36198

5.4 MEDIUM

📋 TL;DR

This stored Cross-Site Scripting (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 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: Affects form fields that don't properly sanitize user input. The vulnerability is stored/persistent, meaning malicious scripts remain on the server until removed.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could steal user session cookies, perform actions as authenticated users, redirect to malicious sites, or install malware on victim systems.

🟠

Likely Case

Session hijacking, credential theft, defacement of web pages, or redirection to phishing sites.

🟢

If Mitigated

Limited impact with proper input validation, output encoding, and Content Security Policy (CSP) headers in place.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Exploitation requires the attacker to have access to submit data to vulnerable form fields, which typically requires some level of access or social engineering.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Adobe Experience Manager 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 official distribution channels. 2. Backup your current installation and data. 3. Apply the update following Adobe's upgrade documentation. 4. Restart the AEM service. 5. Verify the update was successful.

🔧 Temporary Workarounds

Implement Content Security Policy (CSP)

all

Add CSP headers to restrict script execution to trusted sources only.

Add 'Content-Security-Policy' header with appropriate directives in web server configuration

Input Validation and Output Encoding

all

Implement server-side validation and proper output encoding for all user inputs.

Implement input validation libraries and output encoding functions in application code

🧯 If You Can't Patch

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

🔍 How to Verify

Check if Vulnerable:

Check Adobe Experience Manager version via AEM Web Console (/system/console) or by examining the AEM installation directory for version files.

Check Version:

Check /system/console/bundles for org.apache.sling.installer.core bundle version or examine crx-quickstart/VERSION file

Verify Fix Applied:

Verify the version is 6.5.21 or later and test form fields with XSS payloads to ensure they are properly sanitized.

📡 Detection & Monitoring

Log Indicators:

  • Unusual POST requests to form endpoints with script tags or JavaScript code
  • Multiple failed validation attempts on form submissions

Network Indicators:

  • HTTP requests containing script tags or JavaScript in form parameters
  • Unexpected outbound connections from user browsers after visiting AEM pages

SIEM Query:

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

🔗 References

📤 Share & Export