Multiple large organizations were found to be impacted by an authentication bypass in Adobe Experience Manager CRX Package Manager, according to a warning from security vendor Detectify.
The Adobe Experience Manager (AEM) is a content management solution (CMS) used for the building of websites and mobile applications, while also allowing developers to manage marketing content and assets.
The authentication bypass, which was discovered by Detectify Crowdsource community researchers Ai Ho and Bao Bui, could be abused by attackers to access the CRX Package Manager, which is used for managing packages on the local AEM installation.
“The CRX Package Manager is accessed by bypassing authentication in Dispatcher, Adobe Experience Manager’s caching and/or load balancing tool. Dispatcher checks user’s access permissions for a page before delivering the cached page and is an essential part of most – if not all AEM installations. It can be bypassed by adding a lot of special characters in combination in the request: %0a;,” the company said in an advisory.
[ Related: Major Security Flaws in PDF Reader, Photoshop ]
Thus, an attacker able to access the CRX Package Manager could upload a malicious package and then abuse it to execute arbitrary code remotely and take over the vulnerable application.
According to Detectify, there are more than “30 instances of the AEM CRX Bypass vulnerability” present in current enterprise environments.
Some of the affected organizations include LinkedIn, MasterCard, Sony’s PlayStation, and McAfee. The issue was reported to PlayStation in December 2020 and to MasterCard in March 2021. Adobe was informed in March as well, and released a patch in May 2021.
To mitigate the issue, one could block public access to the CRX console (by denying access to endpoints: /crx/*), Detectify said.
UPDATE 07/12/2021 – Adobe has issued the following statement:
For clarification, this issue does not impact AEM Cloud Service customers and only potentially impacts AEM on-premise or AEM as a Managed Service if default security configurations are removed.
As a result, this does not require a CVE from Adobe because AEM has the necessary security controls enabled by default to help protect customers. This out-of-the-box protection is available on supported versions of AEM.