The following has evaluated to null or missing:
==> parentCategory.id [in template "template_id" at line 189, column 201]
----
Tip: It's the step after the last dot that caused this error, not those before it.
----
Tip: If the failing expression is known to legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use [#if myOptionalVar??]when-present[#else]when-missing[/#if]. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)??
----
----
FTL stack trace ("~" means nesting-related):
- Failed at: ${parentCategory.id} [in template "template_id" at line 189, column 199]
----
Elasticsearch and Liferay Enterprise Search Security Advisory: March 2020
Published: March 9, 2020
The following issue may affect the functionality of your Liferay DXP and Enterprise Search environment. This notification provides a description of the latest compatibility change and required actions for Liferay Enterprise Search Subscribers.
Deployments which might be impacted
- Liferay DXP 7.0, 7.1 and 7.2 on Elastic Stack 6 or 7 using Kibana
Vulnerability Information
(As provided by the vendor.)
Kibana Node.js security flaws (ESA-2020-01)
The version of Node.js shipped in all versions of Kibana prior to 7.6.1 and 6.8.7 contain three security flaws.
CVE-2019-15604 describes a Denial of Service (DoS) flaw in the TLS handling code of Node.js. Successful exploitation of this flaw could result in Kibana crashing.
CVE-2019-15606 and CVE-2019-15605 describe flaws in how Node.js handles malformed HTTP headers. These malformed headers could result in a HTTP request smuggling attack when Kibana is running behind a proxy vulnerable to HTTP request smuggling attacks.
This update upgrades Node.js to version 10.19.0, which is not vulnerable to these issues.
Affected Versions
All versions before 7.6.1 and 6.8.7
Solutions and Mitigations
Administrators running Kibana in an environment with untrusted users should upgrade to version 7.6.1 or 6.8.7. There is no workaround for the DoS issue. It may be possible to mitigate the HTTP request smuggling issues on the proxy server. Please consult your proxy vendor for instructions on how to mitigate HTTP request smuggling attacks.
CVE IDs: CVE-2019-15604, CVE-2019-15606, CVE-2019-15605
Search Engine Compatibility Matrix
Reference the information here for the detailed Elasticsearch compatibility including the compatible connector versions and required patch levels.
Vendor Reference
https://discuss.elastic.co/t/elastic-stack-6-8-7-and-7-6-1-security-update/222136
Elastic, Elasticsearch, and X-Pack are trademarks of Elasticsearch BV, registered in the U.S. and in other countries.