Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Block access to CRX package manager through publish dispatcher #104

Open
veldotshine opened this issue Jun 30, 2021 · 0 comments
Open

Block access to CRX package manager through publish dispatcher #104

veldotshine opened this issue Jun 30, 2021 · 0 comments

Comments

@veldotshine
Copy link
Collaborator

veldotshine commented Jun 30, 2021

Describe the bug

It has been identified that there is a bug in Adobe AEM which allows attackers to bypass authentication and gain access to CRX Package Manager through dispatcher. Packages enable the importing and exporting of repository content, and the Package Manager can be used for configuring, building, downloading, installing and deleting packages on local AEM installations. With access to the CRX Package Manager, an attacker could upload a malicious package in Adobe Experience Manager to leverage it to a Remote Control Execution (RCE) and gain full control of the application. AEM Opencloud has already blocked such endpoints previously.

To Reproduce
Steps to reproduce the behavior:

  1. Create a fullset environment using aem-opencloud v5.2.0
  2. After switch dns, access the below endpoint
  3. http://<dispatcher_end_point>/content/..;/crx/packmgr/service.jsp

Expected behavior
This endpoint should be blocked through publish dispatcher endpoint and redirect/take them to default site error page.

Screenshots
image

Environment (please complete the following information if relevant):

  • Full Set using aem-opencloud v5.2.0

Additional context
This vulnerability can be remediated by blocking public access to the CRX console (blocking all access to endpoints: /content/..;/crx/*) in the dispatcher rules.
Also ensure this path is included in inspec-aem-security, so that it verifies the path is added to blocked list.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant