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

Fingerprint the Adobe Experience Manager CMS framework #1003

Open
wants to merge 3 commits into
base: experimental
Choose a base branch
from

Conversation

thomashartm
Copy link

This pull requests adds a fingerprinter to identify the Adobe Experience Manager (AEM) which is a java and OSGi based content management framework and platform.
AEM driven web sites can be identified by very specific paths referenced from within the HTML source or includes scripts e.g.

  • /etc/design as a primary location of CSS and JS resources
  • The term granite e.g. in the path /libs/granite/token.json which stands for an Adobe internal UI framework
  • /etc.clientlibs which is the a proxy erefrencing so called CSS and JS clientlibraries
  • jcr_content which maps to a subnode of the current page inside AEM's cotent repository

AEM is pretty common among fortune 500 companies and can be pretty challenging to secure if not done right.

…dobe Experience Manager (AEM), which is java based content management framework commonly used in big enterprises. Checks wether certain specific paths can be identified or a servlet engine specific response header value is set.
…to the URL can beused to identify the website as an AEM driven project
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

Successfully merging this pull request may close these issues.

1 participant