What are the risks of using the FreeMarker variables utilLocator, objectUtil, and staticUtil
Written By
Lucas Mesquita
How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!
While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.
Legacy Article
You are viewing an article from our legacy "FastTrack"
publication program, made available for informational purposes. Articles
in this program were published without a requirement for independent
editing or verification and are provided"as is" without
guarantee.
Before using any information from this article, independently verify its
suitability for your situation and project.
Issue
- The variables utilLocator, objectUtil, and staticUtil are restricted and inaccessible to the FreeMarker engine.
- What are the risks of using these variables?
Resolution
- If there are no restrictions, Freemarker templates (ADT) can access critical portal components. Depending on the privilege of this variable, this can cause Freemarker models to access privileged portal resources.
- To mitigate this risk would be that only trusted users should be given the necessary permissions. By limiting who can add/update models in your environment, you can minimize the risk of potential exploitation.
- Review of owners of existing templates may also be required as they have full privileges on the provided templates.
Did this article resolve your issue ?