CVE-2024-36174

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 supported platforms
Default Config Vulnerable: ⚠️ Yes
Notes: Affects form fields that don't properly sanitize user input. Requires attacker to have access to create or modify content.

📦 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 content creation/modification privileges in AEM. The vulnerability is in form field handling.

🛠️ 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 installation guide. 3. Restart the AEM instance. 4. Verify the update was successful.

🔧 Temporary Workarounds

Input Validation and Output Encoding

all

Implement strict input validation and output encoding for all form fields

Implement server-side validation using AEM's XSS API: org.apache.sling.xss.XSSAPI

Content Security Policy

all

Implement strict Content Security Policy headers to limit script execution

Add CSP headers via AEM dispatcher configuration or web server

🧯 If You Can't Patch

  • Implement strict input validation and output encoding for all user-controllable form fields
  • Apply Content Security Policy (CSP) headers to restrict script execution sources
  • Limit user permissions to only necessary content creation/modification capabilities
  • Monitor and audit form submissions for suspicious content

🔍 How to Verify

Check if Vulnerable:

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

Check Version:

Navigate to AEM welcome screen or check /system/console/status-productinfo endpoint

Verify Fix Applied:

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

📡 Detection & Monitoring

Log Indicators:

  • Unusual content modifications
  • Form submissions containing script tags or JavaScript
  • Multiple failed XSS attempts

Network Indicators:

  • Unexpected script loads from external domains
  • Suspicious POST requests to form endpoints

SIEM Query:

source="aem_logs" AND ("script" OR "javascript" OR "onload" OR "onerror") AND ("form" OR "field")

🔗 References

📤 Share & Export