This is an automated email from the ASF dual-hosted git repository.

git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/solr-site.git


The following commit(s) were added to refs/heads/asf-site by this push:
     new 1f0d1aa  Automatic Site Publish by Buildbot
1f0d1aa is described below

commit 1f0d1aa123fb1623506e3baf0a69d9c73e868ea4
Author: buildbot <[email protected]>
AuthorDate: Fri Dec 10 22:22:02 2021 +0000

    Automatic Site Publish by Buildbot
---
 output/feeds/all.atom.xml           | 6 ++----
 output/feeds/solr/security.atom.xml | 6 ++----
 output/news.html                    | 3 +--
 output/security.html                | 3 +--
 4 files changed, 6 insertions(+), 12 deletions(-)

diff --git a/output/feeds/all.atom.xml b/output/feeds/all.atom.xml
index 0766736..4303c64 100644
--- a/output/feeds/all.atom.xml
+++ b/output/feeds/all.atom.xml
@@ -2,14 +2,12 @@
 <feed xmlns="http://www.w3.org/2005/Atom";><title>Apache Solr</title><link 
href="/" rel="alternate"></link><link href="/feeds/all.atom.xml" 
rel="self"></link><id>/</id><updated>2021-12-10T00:00:00+00:00</updated><subtitle></subtitle><subtitle></subtitle><entry><title>Apache
 Solr affected by Apache Log4J CVE-2021-44228</title><link 
href="/apache-solr-affected-by-apache-log4j-cve-2021-44228.html" 
rel="alternate"></link><published>2021-12-10T00:00:00+00:00</published><updated>2021-12-10T00:0
 [...]
 Critical&lt;/p&gt;
 &lt;p&gt;&lt;strong&gt;Versions Affected:&lt;/strong&gt;
-7.0.0 to 7.7.3
-8.0.0 to 8.11.0&lt;/p&gt;
+7.4.0 to 7.7.3, 8.0.0 to 8.11.0&lt;/p&gt;
 &lt;p&gt;&lt;strong&gt;Description:&lt;/strong&gt;
 Apache Solr releases prior to 8.11.1 were using a bundled version of the 
Apache Log4J library vulnerable to RCE. For full impact and additional detail 
consult the Log4J security …&lt;/p&gt;</summary><content 
type="html">&lt;p&gt;&lt;strong&gt;Severity:&lt;/strong&gt;
 Critical&lt;/p&gt;
 &lt;p&gt;&lt;strong&gt;Versions Affected:&lt;/strong&gt;
-7.0.0 to 7.7.3
-8.0.0 to 8.11.0&lt;/p&gt;
+7.4.0 to 7.7.3, 8.0.0 to 8.11.0&lt;/p&gt;
 &lt;p&gt;&lt;strong&gt;Description:&lt;/strong&gt;
 Apache Solr releases prior to 8.11.1 were using a bundled version of the 
Apache Log4J library vulnerable to RCE. For full impact and additional detail 
consult the Log4J security page.&lt;/p&gt;
 &lt;p&gt;Apache Solr releases prior to 7.0 (i.e. all Solr 5 and Solr 6 
releases) use log4j 1.2.17 which may be vulnerable for installations using 
non-default logging configurations. To determine you if you are vulnerable 
please consult the Log4J security page.&lt;/p&gt;
diff --git a/output/feeds/solr/security.atom.xml 
b/output/feeds/solr/security.atom.xml
index 538e43f..a1c7a99 100644
--- a/output/feeds/solr/security.atom.xml
+++ b/output/feeds/solr/security.atom.xml
@@ -2,14 +2,12 @@
 <feed xmlns="http://www.w3.org/2005/Atom";><title>Apache Solr - 
solr/security</title><link href="/" rel="alternate"></link><link 
href="/feeds/solr/security.atom.xml" 
rel="self"></link><id>/</id><updated>2021-12-10T00:00:00+00:00</updated><subtitle></subtitle><subtitle></subtitle><entry><title>Apache
 Solr affected by Apache Log4J CVE-2021-44228</title><link 
href="/apache-solr-affected-by-apache-log4j-cve-2021-44228.html" 
rel="alternate"></link><published>2021-12-10T00:00:00+00:00</publishe [...]
 Critical&lt;/p&gt;
 &lt;p&gt;&lt;strong&gt;Versions Affected:&lt;/strong&gt;
-7.0.0 to 7.7.3
-8.0.0 to 8.11.0&lt;/p&gt;
+7.4.0 to 7.7.3, 8.0.0 to 8.11.0&lt;/p&gt;
 &lt;p&gt;&lt;strong&gt;Description:&lt;/strong&gt;
 Apache Solr releases prior to 8.11.1 were using a bundled version of the 
Apache Log4J library vulnerable to RCE. For full impact and additional detail 
consult the Log4J security …&lt;/p&gt;</summary><content 
type="html">&lt;p&gt;&lt;strong&gt;Severity:&lt;/strong&gt;
 Critical&lt;/p&gt;
 &lt;p&gt;&lt;strong&gt;Versions Affected:&lt;/strong&gt;
-7.0.0 to 7.7.3
-8.0.0 to 8.11.0&lt;/p&gt;
+7.4.0 to 7.7.3, 8.0.0 to 8.11.0&lt;/p&gt;
 &lt;p&gt;&lt;strong&gt;Description:&lt;/strong&gt;
 Apache Solr releases prior to 8.11.1 were using a bundled version of the 
Apache Log4J library vulnerable to RCE. For full impact and additional detail 
consult the Log4J security page.&lt;/p&gt;
 &lt;p&gt;Apache Solr releases prior to 7.0 (i.e. all Solr 5 and Solr 6 
releases) use log4j 1.2.17 which may be vulnerable for installations using 
non-default logging configurations. To determine you if you are vulnerable 
please consult the Log4J security page.&lt;/p&gt;
diff --git a/output/news.html b/output/news.html
index 0496e35..6f665f4 100644
--- a/output/news.html
+++ b/output/news.html
@@ -138,8 +138,7 @@
   <p><strong>Severity:</strong>
 Critical</p>
 <p><strong>Versions Affected:</strong>
-7.0.0 to 7.7.3
-8.0.0 to 8.11.0</p>
+7.4.0 to 7.7.3, 8.0.0 to 8.11.0</p>
 <p><strong>Description:</strong>
 Apache Solr releases prior to 8.11.1 were using a bundled version of the 
Apache Log4J library vulnerable to RCE. For full impact and additional detail 
consult the Log4J security page.</p>
 <p>Apache Solr releases prior to 7.0 (i.e. all Solr 5 and Solr 6 releases) use 
log4j 1.2.17 which may be vulnerable for installations using non-default 
logging configurations. To determine you if you are vulnerable please consult 
the Log4J security page.</p>
diff --git a/output/security.html b/output/security.html
index 00d7a01..f55040f 100644
--- a/output/security.html
+++ b/output/security.html
@@ -222,8 +222,7 @@ Then please disclose responsibly by following <a 
href="https://www.apache.org/se
   <p><strong>Severity:</strong>
 Critical</p>
 <p><strong>Versions Affected:</strong>
-7.0.0 to 7.7.3
-8.0.0 to 8.11.0</p>
+7.4.0 to 7.7.3, 8.0.0 to 8.11.0</p>
 <p><strong>Description:</strong>
 Apache Solr releases prior to 8.11.1 were using a bundled version of the 
Apache Log4J library vulnerable to RCE. For full impact and additional detail 
consult the Log4J security page.</p>
 <p>Apache Solr releases prior to 7.0 (i.e. all Solr 5 and Solr 6 releases) use 
log4j 1.2.17 which may be vulnerable for installations using non-default 
logging configurations. To determine you if you are vulnerable please consult 
the Log4J security page.</p>

Reply via email to