CVE-2024-36170

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 scripts. 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 supported platforms
Default Config Vulnerable: ⚠️ Yes
Notes: Affects both AEM Forms and AEM Sites components with vulnerable form fields.

📦 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, or defacement of web pages through injected content.

🟢

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

Requires attacker to have access to submit data to vulnerable form fields, but exploitation is straightforward once access is obtained.

🛠️ 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. Follow Adobe's upgrade documentation for your deployment type (on-premise or cloud). 3. Apply the update to all affected instances. 4. Restart AEM services.

🔧 Temporary Workarounds

Input Validation and Output Encoding

all

Implement strict input validation and proper output encoding for all user-controllable form fields.

Content Security Policy

all

Implement a strict Content Security Policy header to restrict script execution sources.

Content-Security-Policy: default-src 'self'; script-src 'self'

🧯 If You Can't Patch

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

🔍 How to Verify

Check if Vulnerable:

Check AEM version via AEM Web Console (/system/console) or by examining the AEM installation directory.

Check Version:

Check CRX Package Manager or AEM Web Console for version information

Verify Fix Applied:

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

📡 Detection & Monitoring

Log Indicators:

  • Unusual form submissions with script tags or JavaScript code
  • Multiple failed XSS attempts in access logs

Network Indicators:

  • HTTP requests containing script tags or JavaScript in form parameters

SIEM Query:

source="aem_access.log" AND ("<script" OR "javascript:" OR "onerror=" OR "onload=")

🔗 References

📤 Share & Export