CVE-2024-36143

5.4 MEDIUM

📋 TL;DR

Adobe Experience Manager versions 6.5.20 and earlier contain a stored XSS vulnerability where attackers can inject malicious JavaScript into form fields. When users visit pages containing the compromised fields, their browsers execute the attacker's code. This affects all organizations running vulnerable AEM versions.

💻 Affected Systems

Products:
  • Adobe Experience Manager
Versions: 6.5.20 and earlier
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: Affects both AEM Forms and Sites implementations. Requires attacker access to vulnerable form fields.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could steal administrator session cookies, perform actions as authenticated users, deface websites, or redirect users to malicious sites.

🟠

Likely Case

Attackers inject malicious scripts to steal user session data or credentials from authenticated users visiting compromised pages.

🟢

If Mitigated

With proper input validation and output encoding, malicious scripts would be neutralized before reaching user browsers.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Requires attacker to have access to vulnerable form fields, which typically requires some level of access or social engineering.

🛠️ 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 AEM 6.5.21 or later from Adobe Distribution. 2. Apply the Service Pack following Adobe's upgrade documentation. 3. Restart AEM instances. 4. Verify successful upgrade.

🔧 Temporary Workarounds

Input Validation Filter

all

Implement custom servlet filters to sanitize form field inputs before processing

Implement Java servlet filter with OWASP Java Encoder library for input sanitization

Content Security Policy

all

Implement strict CSP headers to prevent script execution from untrusted sources

Add 'Content-Security-Policy: default-src 'self'; script-src 'self'' to HTTP headers

🧯 If You Can't Patch

  • Implement WAF rules to block XSS payloads in form submissions
  • Disable or restrict access to vulnerable form fields until patching is possible

🔍 How to Verify

Check if Vulnerable:

Check AEM version via CRXDE Lite or OSGi console. If version is 6.5.20 or earlier, system is vulnerable.

Check Version:

curl -u admin:password http://localhost:4502/system/console/status-productinfo | grep 'Adobe Experience Manager'

Verify Fix Applied:

After patching, verify version is 6.5.21 or later and test form fields with XSS payloads to ensure they're sanitized.

📡 Detection & Monitoring

Log Indicators:

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

Network Indicators:

  • HTTP requests containing script tags or JavaScript in form parameters
  • Unusual outbound connections from user browsers after form submissions

SIEM Query:

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

🔗 References

📤 Share & Export