CVE-2024-43734

5.4 MEDIUM

📋 TL;DR

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

💻 Affected Systems

Products:
  • Adobe Experience Manager
Versions: 6.5.21 and earlier
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: Affects both AEM Forms and AEM Sites implementations with 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

Exploitation requires ability to submit data to vulnerable form fields, typically requiring some level of access to the AEM interface.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 6.5.22 or later

Vendor Advisory: https://helpx.adobe.com/security/products/experience-manager/apsb24-69.html

Restart Required: Yes

Instructions:

1. Download AEM 6.5.22 or later from Adobe's distribution portal. 2. Apply the Service Pack following Adobe's upgrade documentation. 3. Restart the AEM instance. 4. Verify the update was successful.

🔧 Temporary Workarounds

Input Validation Filter

all

Implement custom servlet filters to sanitize user input in form submissions

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: script-src 'self'' to HTTP response headers

🧯 If You Can't Patch

  • Implement web application firewall (WAF) rules to block XSS payloads in form submissions
  • Disable or restrict access to vulnerable form components until patching is possible

🔍 How to Verify

Check if Vulnerable:

Check AEM version via CRXDE Lite or system console. If version is 6.5.21 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.22 or later and test form fields with XSS payloads to ensure they're properly sanitized.

📡 Detection & Monitoring

Log Indicators:

  • Unusual POST requests to form endpoints with script tags or JavaScript payloads
  • Multiple failed login attempts followed by form submissions

Network Indicators:

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

SIEM Query:

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

🔗 References

📤 Share & Export