Any plan to add compatibility to 7.2?

[jpatel3]

(It's not an issue with django-haystack)

https://www.cvedetails.com/cve/CVE-2017-12629/
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.

It affects Solr version - 5.5 to 7.0.1
Solr contributor suggests, that adding -Ddisable.configEdit=true while restarting to solve it temporarily, until the proper fix is available, but upgrading to 7.2 should also help in avoiding this critical vulnerability.

Configuration

• Operating system version: CentOS
• Search engine version: Solr 6.5.1
• Python version: 2.7
• Django version: 1.9.9
• Haystack version: 2.5.0

[acdha]

Have you tried using Haystack with 7.2? If they didn't have a backwards-incompatible change with the query or update handlers it should work — the Solr team is usually quite conscientious about that.

[ppmdo]

@acdha Did 7.2 work?

[jpatel3]

Haven't tried yet? But I'll have some time this week. I can update here by Friday on it, once I test it.

[ppmdo]

Just tested Solr 7.3.0. I can confirm it works.