CVE-2024-43743

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.21 and earlier.

💻 Affected Systems

Products:
  • Adobe Experience Manager
Versions: 6.5.21 and earlier
Operating Systems: All supported platforms
Default Config Vulnerable: ⚠️ Yes
Notes: All installations 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 risk is reduced to minimal, though the vulnerability still exists in the codebase.

🌐 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 user privileges.

🛠️ 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 Adobe Experience Manager 6.5.22 or later from Adobe's official distribution. 2. Follow Adobe's upgrade documentation for your specific deployment type (AEM as a Cloud Service, AEM on-premise, or AMS). 3. Apply the update to all affected instances. 4. Restart the AEM service.

🔧 Temporary Workarounds

Input Validation and Output Encoding

all

Implement strict input validation and proper output encoding for all form fields to prevent script injection.

Content Security Policy (CSP)

all

Implement a strict Content Security Policy to mitigate the impact of successful XSS attacks.

🧯 If You Can't Patch

  • Implement Web Application Firewall (WAF) rules to detect and block XSS payloads
  • Restrict user access to vulnerable form fields and implement additional input validation layers

🔍 How to Verify

Check if Vulnerable:

Check your AEM version via the AEM Welcome screen or by examining the CRX package manager version.

Check Version:

Navigate to http://[aem-host]:[port]/system/console/status-productinfo or check the AEM Welcome page

Verify Fix Applied:

Verify the AEM version is 6.5.22 or later and test form fields with XSS payloads to ensure they are properly 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

SIEM Query:

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

🔗 References

📤 Share & Export