CVE-2024-36152

5.4 MEDIUM

📋 TL;DR

This stored Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager allows attackers to inject malicious JavaScript into form fields, which executes in victims' browsers when they view the compromised page. It affects users of Adobe Experience Manager versions 6.5.20 and earlier, potentially leading to session hijacking or data theft.

💻 Affected Systems

Products:
  • Adobe Experience Manager
Versions: 6.5.20 and earlier
Operating Systems: All supported OS for AEM
Default Config Vulnerable: ⚠️ Yes
Notes: Affects form fields in AEM; no specific configuration changes required for exploitation.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could steal session cookies, redirect users to malicious sites, or perform actions on behalf of authenticated users, leading to full account compromise.

🟠

Likely Case

Attackers inject scripts to steal user credentials or session tokens, resulting in unauthorized access to sensitive data.

🟢

If Mitigated

With input validation and output encoding, the risk is reduced to minimal, preventing script execution.

🌐 Internet-Facing: HIGH, as public-facing AEM instances are directly accessible, increasing exposure to exploitation.
🏢 Internal Only: MEDIUM, as internal users could still be targeted via phishing or compromised accounts, but network isolation reduces external attacks.

🎯 Exploit Status

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

Exploitation requires access to inject into vulnerable form fields, typically needing some level of user interaction or permissions.

🛠️ 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. Backup your AEM instance. 2. Download and apply the latest patch from Adobe's security updates page. 3. Restart the AEM service to apply changes. 4. Verify the patch by checking the version.

🔧 Temporary Workarounds

Input Validation and Sanitization

all

Implement server-side input validation and output encoding for all form fields to block malicious scripts.

Configure AEM's XSS protection filters and custom validation rules in your code.

🧯 If You Can't Patch

  • Restrict access to AEM admin interfaces and form submission endpoints using network ACLs or WAF rules.
  • Monitor logs for suspicious activity, such as unusual script injections or form submissions, and educate users on safe browsing.

🔍 How to Verify

Check if Vulnerable:

Check the AEM version via the admin console or by running 'java -jar aem-quickstart.jar -version' and compare to affected versions.

Check Version:

java -jar aem-quickstart.jar -version

Verify Fix Applied:

After patching, verify the version is 6.5.21 or later and test form fields for XSS by attempting to inject scripts to ensure they are sanitized.

📡 Detection & Monitoring

Log Indicators:

  • Unusual POST requests to form endpoints with script-like payloads in parameters.
  • Errors or warnings related to XSS filter bypass in AEM logs.

Network Indicators:

  • HTTP requests containing JavaScript code in form data, especially to vulnerable AEM paths.

SIEM Query:

source="aem_logs" AND (message="*script*" OR message="*XSS*")

🔗 References

📤 Share & Export