Upgrading to lucene 7.1.x to fix

[sachinkumaranumula]

Github security scanner points this out. Would you like to comment that ongdb is not prone to this exploit?

Remediation Upgrade org.apache.lucene:lucene-core to version 7.1.0 or later. For example:

<dependency>
  <groupId>org.apache.lucene</groupId>
  <artifactId>lucene-core</artifactId>
  <version>[7.1.0,)</version>
</dependency>

Always verify the validity and compatibility of suggestions with your codebase.

CVE-2017-12629 high severity Vulnerable versions: < 7.1.0 Patched version: 7.1.0 Remote code execution occurs in Apache Solr before 7.1 with Apache Lucene before 7.1 by exploiting XXE in conjunction with use of a Config API add-listener command to reach the RunExecutableListener class. Elasticsearch, although it uses Lucene, is NOT vulnerable to this. Note that the XML external entity expansion vulnerability occurs in the XML Query Parser which is available, by default, for any query request with parameters deftype=xmlparser and can be exploited to upload malicious data to the /upload request handler or as Blind XXE using ftp wrapper in order to read arbitrary local files from the Solr server. Note also that the second vulnerability relates to remote code execution using the RunExecutableListener available on all affected versions of Solr.

[jmsuhy]

I need to verify. I will verify against the 3.5.8 branch and get back to you.

[jmsuhy]

There may be issues upgrading lucene - we most likely want to keep it as it is in Neo4j core - as I am assuming they would have upgraded it if it did not cause issues. We can test an upgrade and see if tests start failing.

[bradnussbaum]

This will be upgraded in future releases. Closing now.