You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@lucene.apache.org by bu...@apache.org on 2019/11/18 13:33:23 UTC

svn commit: r1053053 - in /websites/staging/lucene/trunk/content: ./ solr/news.html

Author: buildbot
Date: Mon Nov 18 13:33:22 2019
New Revision: 1053053

Log:
Staging update by buildbot for lucene

Modified:
    websites/staging/lucene/trunk/content/   (props changed)
    websites/staging/lucene/trunk/content/solr/news.html

Propchange: websites/staging/lucene/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Nov 18 13:33:22 2019
@@ -1 +1 @@
-1869972
+1869973

Modified: websites/staging/lucene/trunk/content/solr/news.html
==============================================================================
--- websites/staging/lucene/trunk/content/solr/news.html (original)
+++ websites/staging/lucene/trunk/content/solr/news.html Mon Nov 18 13:33:22 2019
@@ -196,7 +196,8 @@
 h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
 <h1 id="solr-news">Solr<sup>&trade;</sup> News<a class="headerlink" href="#solr-news" title="Permanent link">&para;</a></h1>
 <h2 id="18-november-2019-cve-2019-12409-apache-solr-rce-vulnerability-due-to-bad-config-default">18 November 2019, CVE-2019-12409: Apache Solr RCE vulnerability due to bad config default<a class="headerlink" href="#18-november-2019-cve-2019-12409-apache-solr-rce-vulnerability-due-to-bad-config-default" title="Permanent link">&para;</a></h2>
-<p><strong>Severity:</strong> High</p>
+<p><strong>Severity:</strong><br />
+High</p>
 <p><strong>Vendor:</strong><br />
 The Apache Software Foundation</p>
 <p><strong>Versions Affected:</strong><br />
@@ -212,8 +213,8 @@ without any authentication. If this port
 in your firewall, then anyone with network access to your Solr nodes
 will be able to access JMX, which may in turn allow them to upload
 malicious code for execution on the Solr server.</p>
-<p>The vulnerability is already public <a href="https://www.apache.org/dyn/closer.cgi/lucene/solr/ref-guide/">1</a> and mitigation steps were
-announced on project mailing lists and news page <a href="https://www.apache.org/dyn/closer.cgi/lucene/solr/ref-guide/">3</a> on August 14th,
+<p>The vulnerability is already public [1] and mitigation steps were
+announced on project mailing lists and news page [3] on August 14th,
 without mentioning RCE at that time.</p>
 <p><strong>Mitigation:</strong><br />
 Make sure your effective solr.in.sh file has ENABLE_REMOTE_JMX_OPTS set
@@ -230,8 +231,8 @@ nodes directly in a hostile network envi
 Matei "Mal" Badanoiu<br />
 Solr JIRA user 'jnyryan' (John)</p>
 <p><strong>References:</strong><br />
-<a href="https://www.apache.org/dyn/closer.cgi/lucene/solr/ref-guide/">1</a> https://issues.apache.org/jira/browse/SOLR-13647<br />
-<a href="https://www.apache.org/dyn/closer.cgi/lucene/solr/ref-guide/">3</a> https://lucene.apache.org/solr/news.html
+[1] https://issues.apache.org/jira/browse/SOLR-13647<br />
+[3] https://lucene.apache.org/solr/news.html
 </code></p>
 <h2 id="2-november-2019-apache-solrtm-830-available">2 November 2019, Apache Solr™ 8.3.0 available<a class="headerlink" href="#2-november-2019-apache-solrtm-830-available" title="Permanent link">&para;</a></h2>
 <p>The Lucene PMC is pleased to announce the release of Apache Solr 8.3.0.</p>