CVE-2024-36146

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 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 supported platforms
Default Config Vulnerable: ⚠️ Yes
Notes: All deployments with vulnerable form fields are affected regardless of configuration.

📦 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 with access to vulnerable forms could inject scripts that steal user session data or perform limited malicious actions within the application context.

🟢

If Mitigated

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

🌐 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 application 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. Follow Adobe's upgrade documentation for your deployment type (on-premise or cloud). 3. Restart all AEM instances after applying the update.

🔧 Temporary Workarounds

Input Validation Filter

all

Implement server-side input validation to sanitize form field inputs before processing.

Implement custom servlet filter or use AEM's built-in XSS protection features

Content Security Policy

all

Deploy Content Security Policy headers to restrict script execution sources.

Add 'Content-Security-Policy' header to web server configuration

🧯 If You Can't Patch

  • Restrict access to vulnerable form fields using AEM permissions
  • Implement web application firewall rules to block XSS payloads

🔍 How to Verify

Check if Vulnerable:

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

Check Version:

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

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 form submissions with script tags
  • Requests containing common XSS payload patterns

Network Indicators:

  • HTTP requests with script payloads in form parameters

SIEM Query:

source="aem-access.log" AND ("<script>" OR "javascript:" OR "onerror=" OR "onload=")

🔗 References

📤 Share & Export