| <!doctype html> |
| <html> |
| <head> |
| <!-- |
| Licensed to the Apache Software Foundation (ASF) under one or more |
| contributor license agreements. See the NOTICE file distributed with |
| this work for additional information regarding copyright ownership. |
| The ASF licenses this file to You under the Apache License, Version 2.0 |
| (the "License"); you may not use this file except in compliance with |
| the License. You may obtain a copy of the License at |
| |
| http://www.apache.org/licenses/LICENSE- 2.0 |
| |
| Unless required by applicable law or agreed to in writing, software |
| distributed under the License is distributed on an "AS IS" BASIS, |
| WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. |
| See the License for the specific language governing permissions and |
| limitations under the License. |
| --> |
| <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> |
| <meta name="viewport" content="minimal-ui, initial-scale=1, maximum-scale=1, user-scalable=0"> |
| |
| <link href='//fonts.googleapis.com/css?family=Raleway:400,300,600,500' rel='stylesheet' type='text/css'> |
| <link href="//maxcdn.bootstrapcdn.com/font-awesome/4.1.0/css/font-awesome.min.css" rel="stylesheet"> |
| <link rel="stylesheet" href="/theme/css/lib/foundation/normalize.css?v=4dd59757" /> |
| <link rel="stylesheet" href="/theme/css/lib/foundation/foundation.min.css?v=4dd59757"/> |
| <link rel="stylesheet" href="/theme/css/lib/foundation/foundation-icons.css?v=4dd59757"/> |
| <link rel="stylesheet" type="text/css" href="//cdn.jsdelivr.net/jquery.slick/1.3.7/slick.css"/> |
| <link rel="stylesheet" href="/theme/css/base.css?v=4dd59757" /> |
| <meta name="Distribution" content="Global"/> |
| <meta name="Robots" content="index,follow"/> |
| |
| <script src="/theme/javascript/lib/jquery-2.1.1.min.js"></script> |
| <script src="/theme/javascript/lib/foundation/modernizr.js?v=4dd59757"></script> |
| <script src="/theme/javascript/lib/angularjs/angular.min.js?v=4dd59757"></script> |
| <script src="/theme/javascript/lib/angularjs/angular-animate.min.js?v=4dd59757"></script> |
| <script src="/theme/javascript/lib/foundation/foundation.min.js?v=4dd59757"></script> |
| <script src="//cdn.jsdelivr.net/jquery.slick/1.3.7/slick.min.js"/></script> |
| <script src="/theme/javascript/lib/jquery.smooth-scroll.min.js?v=4dd59757"></script> |
| <script src="/theme/javascript/main.js?v=4dd59757"></script> |
| <script src="https://www.apachecon.com/event-images/snippet.js"></script> <title>Solr™ Security News - Apache Solr</title> |
| |
| <meta name="keywords" |
| content="apache, apache lucene, apache solr, solr, lucene, |
| search, information retrieval, spell checking, faceting, inverted index, open source"/> |
| <meta property="og:type" content="website" /> |
| <meta property="og:url" content="https://solr.apache.org/security.html"/> |
| <meta property="og:title" content="Solr™ Security News"/> |
| <meta property="og:description" content="How to report a security issue Published CVEs Detected by Scanners Every CVE that is detected by a software scanner is by definition..."/> |
| <meta property="og:image" content="https://solr.apache.org/theme/images/solr_og_image.png?v=4dd59757"/> |
| <meta property="og:image:secure_url" content="https://solr.apache.org/theme/solr/solr_og_image.png?v=4dd59757"/> |
| |
| <link rel="icon" href="/theme/images/favicon.ico" type="image/x-icon"> |
| <link rel="shortcut icon" href="/theme/images/favicon.ico" type="image/x-icon"> |
| <link rel="alternate" type="application/atom+xml" title="Solr security announce feed" href="/feeds/solr/security.atom.xml" /> </head> |
| |
| <body class="page " x-ng-app-root="/solr" x-ng-app="page" x-ng-controller="page.controllers.main"> |
| <div class="contain-to-grid"> |
| <div class="header-section"> |
| <nav class="top-bar" data-topbar role="navigation"> |
| <ul class="title-area"> |
| <li class="name"> |
| <a href="/"><img class="logo" src="/theme/images/logo.svg" /></a> |
| </li> |
| <li class="toggle-topbar menu-icon"><a href="#"><span>Menu</span></a></li> |
| </ul> |
| |
| <div class="top-bar-section"> |
| <ul class="navigation right"> |
| <li> |
| <a href="/blog.html">Blog</a> |
| </li> |
| <li> |
| <a href="/news.html">News</a> |
| </li> |
| <li> |
| <a href="/security.html">Security</a> |
| </li> |
| <li> |
| <a href="/features.html">Features</a> |
| </li> |
| <li> |
| <a href="/resources.html">Resources</a> |
| </li> |
| <li> |
| <a href="/community.html">Community</a> |
| </li> |
| <li> |
| <a href="/whoweare.html">Project</a> |
| </li> |
| <li> |
| <a href="/operator/">Solr Operator</a> |
| </li> |
| <!-- TODO Search not working as of feb 2021, disabling |
| <li class="toggle"> |
| <a ng-hide="toggled" ng-click="toggle();" href="#">Search</a> |
| <div id="search"> |
| <form id="quick-search" method="GET" action="https://sematext.com/opensee/solr" name="searchform"> |
| <fieldset> |
| <div ng-show="toggled" class="search-box ng-hide"> |
| <input type="search" name="q" placeholder="Search..." accesskey="q"/> |
| <a class="search-button" type="submit" onclick="this.closest('form').submit();return false;"><img src="/theme/images/magnifying-glass.png"/></a> |
| </div> |
| </fieldset> |
| </form> </div> |
| </li> |
| --> |
| <li> |
| <a class="btn" href="/downloads.html">Download</a> |
| </li> |
| </ul> |
| </div> |
| </nav> |
| </div> |
| </div> |
| |
| <div class="header-fill"></div> |
| <div class="container"> |
| <div class="row"> |
| <div class="small-12 columns"> |
| <style type="text/css"> |
| .headerlink, .elementid-permalink { |
| visibility: hidden; |
| } |
| 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>™</sup> Security News<a class="headerlink" href="#solr-news" title="Permanent link">¶</a></h1> |
| <h2 id="how-to-report-a-security-issue">How to report a security issue</h2> |
| <h3 id="published-cves-detected-by-scanners">Published CVEs Detected by Scanners</h3> |
| <p>Every CVE that is detected by a software scanner is by definition already public knowledge. That means the Solr PMC and the rest of the world probably already know about it.</p> |
| <p>To find a path forward in addressing a detected CVE we suggest the following process for fastest results:</p> |
| <ol> |
| <li>Check <a href="#recent-cve-reports-for-apache-solr">further down this page</a> to see if the CVE is listed as exploitable in Solr.</li> |
| <li>Check the <a href="#cve-reports-for-apache-solr-dependencies">officially published non-exploitable vulnerabilities</a> list to see if the CVE is listed as not exploitable in Solr.</li> |
| <li>Search through the <a href="https://lists.apache.org/list.html?users@solr.apache.org">Solr users mailing list archive</a> to see if anyone else has brought up this dependency CVE.</li> |
| <li>If no one has, then please do <a href="https://solr.apache.org/community.html#mailing-lists-chat">subscribe to the users mailing list</a> and then send an email asking about the CVE.</li> |
| </ol> |
| <h4 id="dos-and-donts">Dos and Don'ts</h4> |
| <ul> |
| <li>Please DO discuss the possible need for library upgrades on the user list.</li> |
| <li>Please DO search Jira for the CVE number to see if we are addressing it already.</li> |
| <li>Please DO create Jira issues and associated pull requests to propose and discuss upgrades of <em>a single specific</em> dependency.</li> |
| <li>Please DO NOT attach a scan report, or paste output of a scan into Jira (just link the CVE instead)</li> |
| <li>Please DO NOT email the security email below with a scan report it will be ignored.</li> |
| <li>Please DO look into automating some of this with <a href="#vex">VEX</a> and share your experience.</li> |
| </ul> |
| <h4 id="use-of-jira">Use of Jira</h4> |
| <p>Jira is for discussing specific development modifications. Any Jira that contains only scan report output, or references multiple dependencies at the same time is likely to be ignored/closed. The large number of folks sending us reports of things that are already known is a serious drag on our (volunteer) time so <strong>please search Jira</strong> before opening a new issue.</p> |
| <h3 id="new-exploits-you-discover-in-solr">New Exploits <span style="color:blue">You</span> Discover in Solr</h3> |
| <p>The Solr PMC greatly appreciates reports of new security vulnerabilities found in Solr itself or demonstrations of exploiting vulnerabilities via dependencies. |
| <strong>It is important not to publish a previously unknown exploit</strong>, or exploit demonstration code on public mailing lists. |
| Please disclose new exploits responsibly by following these <a href="https://www.apache.org/security/">ASF guidelines</a> for reporting. |
| The contact email for reporting newly discovered exploits in Solr is <a href="mailto:security@solr.apache.org">security@solr.apache.org</a>.</p> |
| <p>Before reporting a new exploit ensure that you have tested it against an instance of Solr that is running a <a href="https://solr.apache.org/downloads.html">supported version</a> and has been properly configured with:</p> |
| <ol> |
| <li><strong>Authentication</strong> - Exploits demonstrated without login waste our time because Solr is not meant to run such that the entire world has access to all of its APIs. Running without forcing users to log in is no more valid than running linux with a widely known default root password, or a database with a root account that has no password.</li> |
| <li><strong>Authorization</strong> - It is not an exploit unless the authenticated user was configured with a role that should have prohibited the action, or the action should never be allowed for any user regardless of role. Your report should say why you think this action is not acceptable for the role(s) you tested it with.</li> |
| </ol> |
| <h4 id="vex">VEX</h4> |
| <p>Since the process of checking whether CVEs in dependencies of Solr affect your |
| Solr deployment is tedious and error-prone, we are experimenting with sharing |
| information about advisories that are known (not) to affect Solr in a |
| machine-readable way.</p> |
| <p>File formats to share this information are called 'VEX' formats. A number of |
| such formats are under active development, such as based on |
| <a href="https://cyclonedx.org/capabilities/vex/">CycloneDX</a> and |
| <a href="https://github.com/oasis-tcs/csaf/blob/master/csaf_2.0/prose/csaf-v2-editor-draft.md#45-profile-5-vex">CSAF</a>.</p> |
| <p>We are currently providing vulnerability information in a CycloneDX JSON-based |
| format <a href="/solr.vex.json">here</a>. We are very curious to hear about your experience, |
| and to find out what is still missing to reduce the signal/noise ratio and make |
| these tools more effective. We invite you to join the discussion at the |
| <a href="mailto:security-discuss@community.apache.org">security-discuss</a> |
| <a href="https://www.apache.org/foundation/mailinglists.html">mailinglist</a> or, |
| if you prefer to collaborate in private, contact |
| <a href="mailto:security@apache.org">security@apache.org</a>. It will likely be interesting |
| to know what security scanning/reporting tool you are using, exactly on which |
| artifacts, and if/how its vendor appears to support VEX. We'd be happy to work |
| with you to see if we can provide this information in other variations or formats.</p> |
| <h3 id="more-information">More information</h3> |
| <p>You will find more security related information on our Wiki: <a href="https://cwiki.apache.org/confluence/display/SOLR/SolrSecurity">https://cwiki.apache.org/confluence/display/SOLR/SolrSecurity</a></p> |
| |
| <h1 id="recent-cve-reports-for-apache-solr">Recent CVE reports for Apache Solr</h1> |
| <p>Below is a list of already announced CVE vulnerabilities. These are also available as an <a href="/feeds/solr/security.atom.xml">ATOM feed</a>:</p> |
| |
| <table> |
| <tr> |
| <th width="130">CVE#</th> |
| <th width="95">Date</th> |
| <th>Announcement</th> |
| </tr> |
| <tr> |
| <td><a href="https://nvd.nist.gov/vuln/detail/CVE-2024-31391">CVE-2024-31391</a></td> |
| <td>2024-04-12</td> |
| <td><a href="#cve-2024-31391-solr-operator-liveness-and-readiness-probes-may-leak-basic-auth-credentials">Solr-Operator liveness and readiness probes may leak basic auth credentials</a></td> |
| </tr> |
| <tr> |
| <td><a href="https://nvd.nist.gov/vuln/detail/CVE-2023-50291">CVE-2023-50291</a></td> |
| <td>2024-02-08</td> |
| <td><a href="#cve-2023-50291-apache-solr-can-leak-certain-passwords-due-to-system-property-redaction-logic-inconsistencies">Apache Solr can leak certain passwords due to System Property redaction logic inconsistencies</a></td> |
| </tr> |
| <tr> |
| <td><a href="https://nvd.nist.gov/vuln/detail/CVE-2023-50292">CVE-2023-50292</a></td> |
| <td>2024-02-08</td> |
| <td><a href="#cve-2023-50292-apache-solr-schema-designer-blindly-trusts-all-configsets-possibly-leading-to-rce-by-unauthenticated-users">Apache Solr Schema Designer blindly "trusts" all configsets, possibly leading to RCE by unauthenticated users</a></td> |
| </tr> |
| <tr> |
| <td><a href="https://nvd.nist.gov/vuln/detail/CVE-2023-50298">CVE-2023-50298</a></td> |
| <td>2024-02-08</td> |
| <td><a href="#cve-2023-50298-apache-solr-can-expose-zookeeper-credentials-via-streaming-expressions">Apache Solr can expose ZooKeeper credentials via Streaming Expressions</a></td> |
| </tr> |
| <tr> |
| <td><a href="https://nvd.nist.gov/vuln/detail/CVE-2023-50386">CVE-2023-50386</a></td> |
| <td>2024-02-08</td> |
| <td><a href="#cve-2023-50386-apache-solr-backuprestore-apis-allow-for-deployment-of-executables-in-malicious-configsets">Apache Solr: Backup/Restore APIs allow for deployment of executables in malicious ConfigSets</a></td> |
| </tr> |
| <tr> |
| <td><a href="https://nvd.nist.gov/vuln/detail/CVE-2023-50290">CVE-2023-50290</a></td> |
| <td>2024-01-12</td> |
| <td><a href="#cve-2023-50290-apache-solr-allows-read-access-to-host-environment-variables">Apache Solr allows read access to host environment variables</a></td> |
| </tr> |
| <tr> |
| <td><a href="https://nvd.nist.gov/vuln/detail/CVE-2022-39135">CVE-2022-39135</a></td> |
| <td>2022-11-20</td> |
| <td><a href="#apache-solr-is-vulnerable-to-cve-2022-39135-via-sql-handler">Apache Solr is vulnerable to CVE-2022-39135 via /sql handler</a></td> |
| </tr> |
| <tr> |
| <td><a href="https://nvd.nist.gov/vuln/detail/CVE-2021-44548">CVE-2021-44548</a></td> |
| <td>2021-12-18</td> |
| <td><a href="#cve-2021-44548-apache-solr-information-disclosure-vulnerability-through-dataimporthandler">Apache Solr information disclosure vulnerability through DataImportHandler</a></td> |
| </tr> |
| <tr> |
| <td><a href="https://nvd.nist.gov/vuln/detail/CVE-2021-44228">CVE-2021-44228</a></td> |
| <td>2021-12-10</td> |
| <td><a href="#apache-solr-affected-by-apache-log4j-cve-2021-44228">Apache Solr affected by Apache Log4J CVE-2021-44228</a></td> |
| </tr> |
| <tr> |
| <td><a href="https://nvd.nist.gov/vuln/detail/CVE-2021-27905">CVE-2021-27905</a></td> |
| <td>2021-04-12</td> |
| <td><a href="#cve-2021-27905-ssrf-vulnerability-with-the-replication-handler">SSRF vulnerability with the Replication handler</a></td> |
| </tr> |
| <tr> |
| <td><a href="https://nvd.nist.gov/vuln/detail/CVE-2021-29262">CVE-2021-29262</a></td> |
| <td>2021-04-12</td> |
| <td><a href="#cve-2021-29262-misapplied-zookeeper-acls-can-result-in-leakage-of-configured-authentication-and-authorization-settings">Misapplied Zookeeper ACLs can result in leakage of configured authentication and authorization settings</a></td> |
| </tr> |
| <tr> |
| <td><a href="https://nvd.nist.gov/vuln/detail/CVE-2021-29943">CVE-2021-29943</a></td> |
| <td>2021-04-12</td> |
| <td><a href="#cve-2021-29943-apache-solr-unprivileged-users-may-be-able-to-perform-unauthorized-readwrite-to-collections">Apache Solr Unprivileged users may be able to perform unauthorized read/write to collections</a></td> |
| </tr> |
| <tr> |
| <td><a href="https://nvd.nist.gov/vuln/detail/CVE-2020-13957">CVE-2020-13957</a></td> |
| <td>2020-10-12</td> |
| <td><a href="#cve-2020-13957-the-checks-added-to-unauthenticated-configset-uploads-in-apache-solr-can-be-circumvented">The checks added to unauthenticated configset uploads in Apache Solr can be circumvented</a></td> |
| </tr> |
| <tr> |
| <td><a href="https://nvd.nist.gov/vuln/detail/CVE-2020-13941">CVE-2020-13941</a></td> |
| <td>2020-08-14</td> |
| <td><a href="#cve-2020-13941-apache-solr-information-disclosure-vulnerability">Apache Solr information disclosure vulnerability</a></td> |
| </tr> |
| <tr> |
| <td><a href="https://nvd.nist.gov/vuln/detail/CVE-2019-17558">CVE-2019-17558</a></td> |
| <td>2019-12-30</td> |
| <td><a href="#cve-2019-17558-apache-solr-rce-through-velocityresponsewriter">Apache Solr RCE through VelocityResponseWriter</a></td> |
| </tr> |
| </table> |
| |
| <h2 id="cve-2024-31391-solr-operator-liveness-and-readiness-probes-may-leak-basic-auth-credentials">2024-04-12, CVE-2024-31391: Solr-Operator liveness and readiness probes may leak basic auth credentials |
| <a class="headerlink" href="#cve-2024-31391-solr-operator-liveness-and-readiness-probes-may-leak-basic-auth-credentials" title="Permanent link">¶</a> |
| </h2> |
| <p><strong>Severity:</strong><br> |
| Moderate</p> |
| <p><strong>Versions Affected:</strong><br> |
| Solr Operator 0.3.0 to 0.8.0</p> |
| <p><strong>Description:</strong> |
| Insertion of Sensitive Information into Log File vulnerability in the Apache Solr Operator.</p> |
| <p>The Solr sked to bootstrap Solr security, the operator will enable basic authentication and create several accounts for accessing Solr: including the "solr" and "admin" accounts for use by end-users, and a "k8s-oper" account which the operator uses for its own requests to Solr. |
| One common source of these operator requests is healthchecks: liveness, readiness, and startup probes are all used to determine Solr's health and ability to receive traffic. |
| By default, the operator configures the Solr APIs used for these probes to be exempt from authentication, but users may specifically request that authentication be required on probe endpoints as well. |
| Whenever one of these probes would fail, if authentication was in use, the Solr Operator would create a Kubernetes "event" containing the username and password of the "k8s-oper" account.</p> |
| <p>Within the affected version range, this vulnerability affects any solrcloud resource which (1) bootstrapped security through use of the <code>.solrOptions.security.authenticationType=basic</code> option, and (2) required authentication be used on probes by setting <code>.solrOptions.security.probesRequireAuth=true</code>.</p> |
| <p><strong>Mitigation:</strong> |
| Users are recommended to upgrade to Solr Operator version 0.8.1, which fixes this issue by ensuring that probes no longer print the credentials used for Solr requests. Users may also mitigate the vulnerability by disabling authentication on their healthcheck probes using the setting <code>.solrOptions.security.probesRequireAuth=false</code>.</p> |
| <p><strong>References:</strong><br> |
| JIRA - <a href="https://issues.apache.org/jira/browse/SOLR-17216">SOLR-17216</a><br> |
| CVE - <a href="https://nvd.nist.gov/vuln/detail/CVE-2024-31391">CVE-2024-31391</a></p> |
| <hr/> |
| <h2 id="cve-2023-50291-apache-solr-can-leak-certain-passwords-due-to-system-property-redaction-logic-inconsistencies">2024-02-08, CVE-2023-50291: Apache Solr can leak certain passwords due to System Property redaction logic inconsistencies |
| <a class="headerlink" href="#cve-2023-50291-apache-solr-can-leak-certain-passwords-due-to-system-property-redaction-logic-inconsistencies" title="Permanent link">¶</a> |
| </h2> |
| <p><strong>Severity:</strong><br> |
| Moderate</p> |
| <p><strong>Versions Affected:</strong></p> |
| <ul> |
| <li>Apache Solr 6.0.0 through 8.11.2</li> |
| <li>Apache Solr 9.0.0 before 9.3.0</li> |
| </ul> |
| <p><strong>Description:</strong><br> |
| Insufficiently Protected Credentials vulnerability in Apache Solr.</p> |
| <p>This issue affects Apache Solr: from 6.0.0 through 8.11.2, from 9.0.0 before 9.3.0. |
| One of the two endpoints that publishes the Solr process' Java system properties, /admin/info/properties, was only setup to hide system properties that had "password" contained in the name. |
| There are a number of sensitive system properties, such as "basicauth" and "aws.secretKey" do not contain "password", thus their values were published via the "/admin/info/properties" endpoint. |
| This endpoint populates the list of System Properties on the home screen of the Solr Admin page, making the exposed credentials visible in the UI.</p> |
| <p>This /admin/info/properties endpoint is protected under the "config-read" permission. |
| Therefore, Solr Clouds with Authorization enabled will only be vulnerable through logged-in users that have the "config-read" permission. |
| Users are recommended to upgrade to version 9.3.0 or 8.11.3, which fixes the issue. |
| A single option now controls hiding Java system property for all endpoints, "-Dsolr.hiddenSysProps". |
| By default all known sensitive properties are hidden (including "-Dbasicauth"), as well as any property with a name containing "secret" or "password".</p> |
| <p>Users who cannot upgrade can also use the following Java system property to fix the issue:<br> |
| <code>-Dsolr.redaction.system.pattern=".*(password|secret|basicauth).*"</code></p> |
| <p><strong>Mitigation:</strong><br> |
| Users are recommended to upgrade to version 8.11.3, 9.3.0 or later, which has consistent systemProperty redaction logic.</p> |
| <p><strong>Credit:</strong> |
| Michael Taggart (reporter)</p> |
| <p><strong>References:</strong><br> |
| JIRA - <a href="https://issues.apache.org/jira/browse/SOLR-16809">SOLR-16809</a><br> |
| CVE - <a href="https://nvd.nist.gov/vuln/detail/CVE-2023-50291">CVE-2023-50291</a></p> |
| <hr/> |
| <h2 id="cve-2023-50292-apache-solr-schema-designer-blindly-trusts-all-configsets-possibly-leading-to-rce-by-unauthenticated-users">2024-02-08, CVE-2023-50292: Apache Solr Schema Designer blindly "trusts" all configsets, possibly leading to RCE by unauthenticated users |
| <a class="headerlink" href="#cve-2023-50292-apache-solr-schema-designer-blindly-trusts-all-configsets-possibly-leading-to-rce-by-unauthenticated-users" title="Permanent link">¶</a> |
| </h2> |
| <p><strong>Severity:</strong><br> |
| Moderate</p> |
| <p><strong>Versions Affected:</strong></p> |
| <ul> |
| <li>Apache Solr 6.0.0 through 8.11.2</li> |
| <li>Apache Solr 9.0.0 before 9.3.0</li> |
| </ul> |
| <p><strong>Description:</strong><br> |
| Incorrect Permission Assignment for Critical Resource, Improper Control of Dynamically-Managed Code Resources vulnerability in Apache Solr.</p> |
| <p>This issue affects Apache Solr: from 8.10.0 through 8.11.2, from 9.0.0 before 9.3.0.</p> |
| <p>The Schema Designer was introduced to allow users to more easily configure and test new Schemas and configSets. |
| However, when the feature was created, the "trust" (authentication) of these configSets was not considered. |
| External library loading is only available to configSets that are "trusted" (created by authenticated users), thus non-authenticated users are unable to perform Remote Code Execution. |
| Since the Schema Designer loaded configSets without taking their "trust" into account, configSets that were created by unauthenticated users were allowed to load external libraries when used in the Schema Designer.</p> |
| <p><strong>Mitigation:</strong><br> |
| Users are recommended to upgrade to version 8.11.3, 9.3.0 or later.</p> |
| <p><strong>Credit:</strong> |
| Skay (reporter)</p> |
| <p><strong>References:</strong><br> |
| JIRA - <a href="https://issues.apache.org/jira/browse/SOLR-16777">SOLR-16777</a><br> |
| CVE - <a href="https://nvd.nist.gov/vuln/detail/CVE-2023-50292">CVE-2023-50292</a></p> |
| <hr/> |
| <h2 id="cve-2023-50298-apache-solr-can-expose-zookeeper-credentials-via-streaming-expressions">2024-02-08, CVE-2023-50298: Apache Solr can expose ZooKeeper credentials via Streaming Expressions |
| <a class="headerlink" href="#cve-2023-50298-apache-solr-can-expose-zookeeper-credentials-via-streaming-expressions" title="Permanent link">¶</a> |
| </h2> |
| <p><strong>Severity:</strong><br> |
| Low</p> |
| <p><strong>Versions Affected:</strong></p> |
| <ul> |
| <li>Apache Solr 6.0.0 through 8.11.2</li> |
| <li>Apache Solr 9.0.0 before 9.4.1</li> |
| </ul> |
| <p><strong>Description:</strong><br> |
| Exposure of Sensitive Information to an Unauthorized Actor vulnerability in Apache Solr.This issue affects Apache Solr: from 6.0.0 through 8.11.2, from 9.0.0 before 9.4.1.</p> |
| <p>Solr Streaming Expressions allows users to extract data from other Solr Clouds, using a "zkHost" parameter. |
| When original SolrCloud is setup to use ZooKeeper credentials and ACLs, they will be sent to whatever "zkHost" the user provides. |
| An attacker could setup a server to mock ZooKeeper, that accepts ZooKeeper requests with credentials and ACLs and extracts the sensitive information, |
| then send a streaming expression using the mock server's address in "zkHost". |
| Streaming Expressions are exposed via the "/streaming" handler, with "read" permissions.</p> |
| <p><strong>Mitigation:</strong><br> |
| Users are recommended to upgrade to version 8.11.3 or 9.4.1, which fix the issue. |
| From these versions on, only zkHost values that have the same server address (regardless of chroot), will use the given ZooKeeper credentials and ACLs when connecting.</p> |
| <p><strong>Credit:</strong> |
| Qing Xu (reporter)</p> |
| <p><strong>References:</strong><br> |
| JIRA - <a href="https://issues.apache.org/jira/browse/SOLR-17098">SOLR-17098</a><br> |
| CVE - <a href="https://nvd.nist.gov/vuln/detail/CVE-2023-50298">CVE-2023-50298</a></p> |
| <hr/> |
| <h2 id="cve-2023-50386-apache-solr-backuprestore-apis-allow-for-deployment-of-executables-in-malicious-configsets">2024-02-08, CVE-2023-50386: Apache Solr: Backup/Restore APIs allow for deployment of executables in malicious ConfigSets |
| <a class="headerlink" href="#cve-2023-50386-apache-solr-backuprestore-apis-allow-for-deployment-of-executables-in-malicious-configsets" title="Permanent link">¶</a> |
| </h2> |
| <p><strong>Severity:</strong><br> |
| Moderate</p> |
| <p><strong>Versions Affected:</strong></p> |
| <ul> |
| <li>Apache Solr 6.0.0 through 8.11.2</li> |
| <li>Apache Solr 9.0.0 before 9.4.1</li> |
| </ul> |
| <p><strong>Description:</strong><br> |
| Improper Control of Dynamically-Managed Code Resources, Unrestricted Upload of File with Dangerous Type, Inclusion of Functionality from Untrusted Control Sphere vulnerability in Apache Solr.This issue affects Apache Solr: from 6.0.0 through 8.11.2, from 9.0.0 before 9.4.1.</p> |
| <p>In the affected versions, Solr ConfigSets accepted Java jar and class files to be uploaded through the ConfigSets API. |
| When backing up Solr Collections, these configSet files would be saved to disk when using the LocalFileSystemRepository (the default for backups). |
| If the backup was saved to a directory that Solr uses in its ClassPath/ClassLoaders, then the jar and class files would be available to use with any ConfigSet, trusted or untrusted.</p> |
| <p>When Solr is run in a secure way (Authorization enabled), as is strongly suggested, this vulnerability is limited to extending the Backup permissions with the ability to add libraries.</p> |
| <p><strong>Mitigation:</strong><br> |
| Users are recommended to upgrade to version 8.11.3 or 9.4.1, which fix the issue. |
| In these versions, the following protections have been added:</p> |
| <ul> |
| <li>Users are no longer able to upload files to a configSet that could be executed via a Java ClassLoader.</li> |
| <li>The Backup API restricts saving backups to directories that are used in the ClassLoader.</li> |
| </ul> |
| <p><strong>Credit:</strong> |
| L3yx (reporter)</p> |
| <p><strong>References:</strong><br> |
| JIRA - <a href="https://issues.apache.org/jira/browse/SOLR-16949">SOLR-16949</a><br> |
| CVE - <a href="https://nvd.nist.gov/vuln/detail/CVE-2023-50386">CVE-2023-50386</a></p> |
| <hr/> |
| <h2 id="cve-2023-50290-apache-solr-allows-read-access-to-host-environment-variables">2024-01-12, CVE-2023-50290: Apache Solr allows read access to host environment variables |
| <a class="headerlink" href="#cve-2023-50290-apache-solr-allows-read-access-to-host-environment-variables" title="Permanent link">¶</a> |
| </h2> |
| <p><strong>Severity:</strong><br> |
| Important</p> |
| <p><strong>Versions Affected:</strong><br> |
| Solr 9.0 to 9.2.1</p> |
| <p><strong>Description:</strong><br> |
| Exposure of Sensitive Information to an Unauthorized Actor vulnerability in Apache Solr. |
| The Solr Metrics API publishes all unprotected environment variables available to each Apache Solr instance. |
| Users are able to specify which environment variables to hide, however, the default list is designed to work for known secret Java system properties. |
| Environment variables cannot be strictly defined in Solr, like Java system properties can be, and may be set for the entire host, unlike Java system properties which are set per-Java-process.</p> |
| <p>The Solr Metrics API is protected by the "metrics-read" permission. |
| Therefore, Solr Clouds with Authorization setup will only be vulnerable via users with the "metrics-read" permission.</p> |
| <p><strong>Mitigation:</strong><br> |
| Users are recommended to upgrade to version 9.3.0 or later, in which environment variables are not published via the Metrics API.</p> |
| <p><strong>References:</strong><br> |
| JIRA - <a href="https://issues.apache.org/jira/browse/SOLR-16808">SOLR-15233</a><br> |
| CVE - <a href="https://nvd.nist.gov/vuln/detail/CVE-2023-50290">CVE-2023-50290</a></p> |
| <hr/> |
| <h2 id="apache-solr-is-vulnerable-to-cve-2022-39135-via-sql-handler">2022-11-20, Apache Solr is vulnerable to CVE-2022-39135 via /sql handler |
| <a class="headerlink" href="#apache-solr-is-vulnerable-to-cve-2022-39135-via-sql-handler" title="Permanent link">¶</a> |
| </h2> |
| <p><strong>Versions Affected:</strong><br> |
| Solr 6.5 to 8.11.2 |
| Solr 9.0</p> |
| <p><strong>Description:</strong><br> |
| Apache Calcite has a vulnerability, CVE-2022-39135, that is exploitable in Apache Solr in SolrCloud mode. If an untrusted user can supply SQL queries to Solr’s “/sql” handler (even indirectly via proxies / other apps), then the user could perform an XML External Entity (XXE) attack. This might have been exposed by some deployers of Solr in order for internal analysts to use JDBC based tooling, but would have unlikely been granted to wider audiences.</p> |
| <p><strong>Impact:</strong><br> |
| An XXE attack may lead to the disclosure of confidential data, denial of service, server side request forgery (SSRF), port scanning from the Solr node, and other system impacts.</p> |
| <p><strong>Mitigation:</strong><br> |
| Most Solr installations don’t make use of the SQL functionality. For such users, the standard Solr security advice of using a firewall should be adequate. Nonetheless, the functionality can be disabled. As of Solr 9, it has been modularized and thus became opt-in, so nothing is needed for Solr 9 users that don’t use it. Users <em>not</em> using SolrCloud can’t use the functionality at all. For other users that wish to disable it, you must register a request handler that masks the underlying functionality in solrconfig.xml like so:</p> |
| <div class="codehilite"><pre><span></span><code><span class="err"> <requestHandler name="/sql" class="solr.NotFoundRequestHandler"/></span> |
| </code></pre></div> |
| |
| <p>Users needing this SQL functionality are forced to upgrade to Solr 9.1. If Solr 8.11.3 is released, then it will be an option as well. Simply replacing Calcite and other JAR files may mostly work but could fail depending on the particulars of the query. Users interested in this or in patching their own versions of Solr should examine SOLR-16421 for a source patch.</p> |
| <p><strong>Credit:</strong><br> |
| Andreas Hubold at CoreMedia GmbH</p> |
| <p><strong>References:</strong><br> |
| JIRA - <a href="https://issues.apache.org/jira/browse/SOLR-16421">SOLR-16421</a><br> |
| CVE - <a href="https://nvd.nist.gov/vuln/detail/CVE-2022-39135">CVE-2022-39135</a></p> |
| <hr/> |
| <h2 id="cve-2021-44548-apache-solr-information-disclosure-vulnerability-through-dataimporthandler">2021-12-18, CVE-2021-44548: Apache Solr information disclosure vulnerability through DataImportHandler |
| <a class="headerlink" href="#cve-2021-44548-apache-solr-information-disclosure-vulnerability-through-dataimporthandler" title="Permanent link">¶</a> |
| </h2> |
| <p><strong>Severity:</strong><br> |
| Moderate</p> |
| <p><strong>Versions Affected:</strong><br> |
| All versions prior to 8.11.1. Affected platforms: Windows.</p> |
| <p><strong>Description:</strong><br> |
| An Improper Input Validation vulnerability in DataImportHandler of Apache Solr allows an attacker to provide a Windows UNC path resulting in an SMB network call being made from the Solr host to another host on the network. If the attacker has wider access to the network, this may lead to SMB attacks, which may result in:</p> |
| <ul> |
| <li>The exfiltration of sensitive data such as OS user hashes (NTLM/LM hashes),</li> |
| <li>In case of misconfigured systems, SMB Relay Attacks which can lead to user impersonation on SMB Shares or, in a worse-case scenario, Remote Code Execution</li> |
| </ul> |
| <p>This issue affects all Apache Solr versions prior to 8.11.1. This issue only affects Windows.</p> |
| <p><strong>Mitigation:</strong><br> |
| Upgrade to Solr 8.11.1, and/or ensure only trusted clients can make requests to Solr's DataImport handler.</p> |
| <p><strong>Credit:</strong><br> |
| Apache Solr would like to thank LaiHan of Nsfocus security team for reporting the issue</p> |
| <p><strong>References:</strong><br> |
| Jira issue <a href="https://issues.apache.org/jira/browse/SOLR-15826">SOLR-15826</a></p> |
| <hr/> |
| <h2 id="apache-solr-affected-by-apache-log4j-cve-2021-44228">2021-12-10, Apache Solr affected by Apache Log4J CVE-2021-44228 |
| <a class="headerlink" href="#apache-solr-affected-by-apache-log4j-cve-2021-44228" title="Permanent link">¶</a> |
| </h2> |
| <p><strong>Severity:</strong> |
| Critical</p> |
| <p><strong>Versions Affected:</strong> |
| 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.4 (i.e. Solr 5, Solr 6, and Solr 7 through 7.3) use Log4J 1.2.17 which may be vulnerable for installations using non-default logging configurations that include the JMS Appender, see <a href="https://github.com/apache/logging-log4j2/pull/608#issuecomment-990494126">https://github.com/apache/logging-log4j2/pull/608#issuecomment-990494126</a> for discussion.</p> |
| <p>Solr's Prometheus Exporter uses Log4J as well but it does not log user input or data, so we don't see a risk there.</p> |
| <p>Solr is <em>not</em> vulnerable to the followup <strong>CVE-2021-45046</strong> and <strong>CVE-2021-45105</strong>. A listing of these and other CVEs with some justifications are listed in Solr's wiki: <a href="https://cwiki.apache.org/confluence/display/SOLR/SolrSecurity#SolrSecurity-SolrandVulnerabilityScanningTools">https://cwiki.apache.org/confluence/display/SOLR/SolrSecurity#SolrSecurity-SolrandVulnerabilityScanningTools</a></p> |
| <p><strong>Mitigation:</strong> |
| Any of the following are enough to prevent this vulnerability for Solr servers:</p> |
| <ul> |
| <li>Upgrade to <code>Solr 8.11.1</code> or greater (when available), which will include an updated version (<code>>= 2.16.0</code>) of the Log4J dependency.</li> |
| <li>If you are using Solr's official docker image, it has already been mitigated in all versions listed as supported on Docker Hub: <a href="https://hub.docker.com/_/solr">https://hub.docker.com/_/solr</a>. You may need to re-pull the image.</li> |
| <li>Manually update the version of Log4J on your runtime classpath and restart your Solr application.</li> |
| <li>(Linux/MacOS) Edit your <code>solr.in.sh</code> file to include: |
| <code>SOLR_OPTS="$SOLR_OPTS -Dlog4j2.formatMsgNoLookups=true"</code></li> |
| <li>(Windows) Edit your <code>solr.in.cmd</code> file to include: |
| <code>set SOLR_OPTS=%SOLR_OPTS% -Dlog4j2.formatMsgNoLookups=true</code></li> |
| <li>Follow any of the other mitgations listed at <a href="https://logging.apache.org/log4j/2.x/security.html">https://logging.apache.org/log4j/2.x/security.html</a></li> |
| </ul> |
| <p>The Log4J security page refers to setting <code>log4j2.formatMsgNoLookups=true</code> as a "discredited" mitigation. In reality, it depends. |
| We've looked at the root cause and audited the code paths that lead to the vulnerability, and we feel confident in this mitigation being sufficient for Solr. |
| See <a href="https://lists.apache.org/thread/kgh63sncrsm2bls884pg87mnt8vqztmz">https://lists.apache.org/thread/kgh63sncrsm2bls884pg87mnt8vqztmz</a> for discussion.</p> |
| <p><strong>References:</strong> |
| <a href="https://logging.apache.org/log4j/2.x/security.html">https://logging.apache.org/log4j/2.x/security.html</a></p> |
| <hr/> |
| <h2 id="cve-2021-27905-ssrf-vulnerability-with-the-replication-handler">2021-04-12, CVE-2021-27905: SSRF vulnerability with the Replication handler |
| <a class="headerlink" href="#cve-2021-27905-ssrf-vulnerability-with-the-replication-handler" title="Permanent link">¶</a> |
| </h2> |
| <p><strong>Severity:</strong> |
| High</p> |
| <p><strong>Versions Affected:</strong> |
| 7.0.0 to 7.7.3 |
| 8.0.0 to 8.8.1</p> |
| <p><strong>Description:</strong> |
| The ReplicationHandler (normally registered at "/replication" under a Solr core) has a "masterUrl" (also "leaderUrl" alias) parameter that is used to designate another ReplicationHandler on another Solr core to replicate index data into the local core. |
| To prevent a SSRF vulnerability, Solr ought to check these parameters against a similar configuration it uses for the "shards" parameter. Prior to this bug getting fixed, it did not.</p> |
| <p><strong>Mitigation:</strong> |
| Any of the following are enough to prevent this vulnerability:</p> |
| <ul> |
| <li>Upgrade to <code>Solr 8.8.2</code> or greater.</li> |
| <li>If upgrading is not an option, consider applying the patch in <a href="https://issues.apache.org/jira/browse/SOLR-15217">SOLR-15217</a></li> |
| <li>Ensure that any access to the replication handler is purely internal to Solr. Typically, it's only accessed externally for diagnostic/informational purposes.</li> |
| </ul> |
| <p><strong>Credit:</strong> |
| Reported by Caolinhong(Skay) from QI-ANXIN Cert (QI-ANXIN Technology Group Inc.)</p> |
| <p><strong>References:</strong> |
| <a href="https://issues.apache.org/jira/browse/SOLR-15217">SOLR-15217</a>: CVE-2021-27905: SSRF vulnerability with the Replication handler</p> |
| <hr/> |
| <h2 id="cve-2021-29262-misapplied-zookeeper-acls-can-result-in-leakage-of-configured-authentication-and-authorization-settings">2021-04-12, CVE-2021-29262: Misapplied Zookeeper ACLs can result in leakage of configured authentication and authorization settings |
| <a class="headerlink" href="#cve-2021-29262-misapplied-zookeeper-acls-can-result-in-leakage-of-configured-authentication-and-authorization-settings" title="Permanent link">¶</a> |
| </h2> |
| <p><strong>Severity:</strong> |
| High</p> |
| <p><strong>Versions Affected:</strong> |
| 7.0.0 to 7.7.3 |
| 8.0.0 to 8.8.1</p> |
| <p><strong>Description:</strong> |
| When starting Apache Solr versions prior to 8.8.2, configured with the SaslZkACLProvider or VMParamsAllAndReadonlyDigestZkACLProvider and no existing security.json znode, if the optional read-only user is configured then Solr would not treat that node as a sensitive path and would allow it to be readable. |
| Additionally, with any ZkACLProvider, if the security.json is already present, Solr will not automatically update the ACLs.</p> |
| <p><strong>Mitigation:</strong> |
| Any of the following are enough to prevent this vulnerability:</p> |
| <ul> |
| <li>Manually set appropriate ACLs on /security.json znode.</li> |
| <li>Upgrade to <code>Solr 8.8.2</code> or greater.</li> |
| <li>If upgrading is not an option, consider applying the patch in <a href="https://issues.apache.org/jira/browse/SOLR-15249">SOLR-15249</a></li> |
| <li>Ensure that any access to zookeeper is only by trusted application.</li> |
| </ul> |
| <p><strong>Credit:</strong> |
| Timothy Potter and Mike Drob, Apple Cloud Services</p> |
| <p><strong>References:</strong> |
| <a href="https://issues.apache.org/jira/browse/SOLR-15249">SOLR-15249</a>: CVE-2021-29262: Misapplied Zookeeper ACLs can result in leakage of configured authentication and authorization settings</p> |
| <hr/> |
| <h2 id="cve-2021-29943-apache-solr-unprivileged-users-may-be-able-to-perform-unauthorized-readwrite-to-collections">2021-04-12, CVE-2021-29943: Apache Solr Unprivileged users may be able to perform unauthorized read/write to collections |
| <a class="headerlink" href="#cve-2021-29943-apache-solr-unprivileged-users-may-be-able-to-perform-unauthorized-readwrite-to-collections" title="Permanent link">¶</a> |
| </h2> |
| <p><strong>Severity:</strong> |
| High</p> |
| <p><strong>Versions Affected:</strong> |
| 7.0.0 to 7.7.3 |
| 8.0.0 to 8.8.1</p> |
| <p><strong>Description:</strong> |
| When using ConfigurableInternodeAuthHadoopPlugin for authentication, Apache Solr versions prior to 8.8.2 would forward/proxy distributed requests using server credentials instead of original client credentials. This would result in incorrect authorization resolution on the receiving hosts.</p> |
| <p><strong>Mitigation:</strong> |
| Any of the following are enough to prevent this vulnerability:</p> |
| <ul> |
| <li>Upgrade to <code>Solr 8.8.2</code> or greater.</li> |
| <li>If upgrading is not an option, consider applying the patch in <a href="https://issues.apache.org/jira/browse/SOLR-15233">SOLR-15233</a></li> |
| <li>Use a different authentication plugin, such as the KerberosPlugin or HadoopAuthPlugin</li> |
| </ul> |
| <p><strong>Credit:</strong> |
| Geza Nagy</p> |
| <p><strong>References:</strong> |
| <a href="https://issues.apache.org/jira/browse/SOLR-15233">SOLR-15233</a>: CVE-2021-29943: Apache Solr Unprivileged users may be able to perform unauthorized read/write to collections </p> |
| <hr/> |
| <h2 id="cve-2020-13957-the-checks-added-to-unauthenticated-configset-uploads-in-apache-solr-can-be-circumvented">2020-10-12, CVE-2020-13957: The checks added to unauthenticated configset uploads in Apache Solr can be circumvented |
| <a class="headerlink" href="#cve-2020-13957-the-checks-added-to-unauthenticated-configset-uploads-in-apache-solr-can-be-circumvented" title="Permanent link">¶</a> |
| </h2> |
| <p><strong>Severity:</strong> |
| High</p> |
| <p><strong>Versions Affected:</strong> |
| 6.6.0 to 6.6.6 |
| 7.0.0 to 7.7.3 |
| 8.0.0 to 8.6.2</p> |
| <p><strong>Description:</strong> |
| Solr prevents some features considered dangerous (which could be used for remote code execution) to be configured in a ConfigSet that's uploaded via API without authentication/authorization. The checks in place to prevent such features can be circumvented by using a combination of UPLOAD/CREATE actions.</p> |
| <p><strong>Mitigation:</strong> |
| Any of the following are enough to prevent this vulnerability:</p> |
| <ul> |
| <li>Disable UPLOAD command in ConfigSets API if not used by setting the system property: <code>configset.upload.enabled</code> to <code>false</code> (<a href="https://solr.apache.org/guide/8_6/configsets-api.html">see docs</a>)</li> |
| <li>Use Authentication/Authorization and make sure unknown requests aren't allowed (<a href="https://solr.apache.org/guide/8_6/authentication-and-authorization-plugins.html">see docs</a>)</li> |
| <li>Upgrade to <code>Solr 8.6.3</code> or greater.</li> |
| <li>If upgrading is not an option, consider applying the patch in <a href="https://issues.apache.org/jira/browse/SOLR-14663">SOLR-14663</a></li> |
| <li>No Solr API, including the Admin UI, is designed to be exposed to non-trusted parties. Tune your firewall so that only trusted computers and people are allowed access</li> |
| </ul> |
| <p><strong>Credit:</strong> |
| Tomás Fernández Löbbe, András Salamon</p> |
| <p><strong>References:</strong> |
| <a href="https://issues.apache.org/jira/browse/SOLR-14925">SOLR-14925</a>: CVE-2020-13957: The checks added to unauthenticated configset uploads can be circumvented</p> |
| <hr/> |
| <h2 id="cve-2020-13941-apache-solr-information-disclosure-vulnerability">2020-08-14, CVE-2020-13941: Apache Solr information disclosure vulnerability |
| <a class="headerlink" href="#cve-2020-13941-apache-solr-information-disclosure-vulnerability" title="Permanent link">¶</a> |
| </h2> |
| <p><strong>Severity:</strong> |
| Medium</p> |
| <p><strong>Versions Affected:</strong><br> |
| Before Solr 8.6. Some risks are specific to Windows.</p> |
| <p><strong>Description:</strong> |
| Reported in SOLR-14515 (private) and fixed in SOLR-14561 (public), released in Solr version 8.6.0. |
| The Replication handler (https://solr.apache.org/guide/8_6/index-replication.html#http-api-commands-for-the-replicationhandler) allows commands backup, restore and deleteBackup. Each of these take a location parameter, which was not validated, i.e you could read/write to any location the solr user can access. </p> |
| <p>On a windows system SMB paths such as \10.0.0.99\share\folder may also be used, leading to:</p> |
| <ul> |
| <li>The possibility of restoring another SolrCore from a server on the network (or mounted remote file system) may lead to:<ul> |
| <li>Exposing search index data that the attacker should otherwise not have access to</li> |
| <li>Replacing the index data entirely by loading it from a remote file system that the attacker controls</li> |
| </ul> |
| </li> |
| <li>Launching SMB attacks which may result in:<ul> |
| <li>The exfiltration of sensitive data such as OS user hashes (NTLM/LM hashes),</li> |
| <li>In case of misconfigured systems, SMB Relay Attacks which can lead to user impersonation on SMB Shares or, in a worse-case scenario, Remote Code Execution </li> |
| </ul> |
| </li> |
| </ul> |
| <p><strong>Mitigation:</strong> |
| Upgrade to Solr 8.6, and/or ensure only trusted clients can make requests of Solr's replication handler.</p> |
| <p><strong>Credit:</strong> |
| Matei "Mal" Badanoiu</p> |
| <hr/> |
| <h2 id="cve-2019-17558-apache-solr-rce-through-velocityresponsewriter">2019-12-30, CVE-2019-17558: Apache Solr RCE through VelocityResponseWriter |
| <a class="headerlink" href="#cve-2019-17558-apache-solr-rce-through-velocityresponsewriter" title="Permanent link">¶</a> |
| </h2> |
| <p><strong>Severity:</strong> High</p> |
| <p><strong>Vendor:</strong><br> |
| The Apache Software Foundation</p> |
| <p><strong>Versions Affected:</strong> |
| 5.0.0 to 8.3.1</p> |
| <p><strong>Description:</strong><br> |
| The affected versions are vulnerable to a Remote Code Execution through the |
| VelocityResponseWriter. A Velocity template can be provided through |
| Velocity templates in a configset <code>velocity/</code> directory or as a parameter. |
| A user defined configset could contain renderable, potentially malicious, |
| templates. Parameter provided templates are disabled by default, but can |
| be enabled by setting <code>params.resource.loader.enabled</code> by defining a |
| response writer with that setting set to <code>true</code>. Defining a response |
| writer requires configuration API access.</p> |
| <p>Solr 8.4 removed the params resource loader entirely, and only enables the |
| configset-provided template rendering when the configset is <code>trusted</code> (has |
| been uploaded by an authenticated user).</p> |
| <p><strong>Mitigation:</strong><br> |
| Ensure your network settings are configured so that only trusted traffic |
| communicates with Solr, especially to the configuration APIs.</p> |
| <p><strong>Credit:</strong><br> |
| Github user <code>s00py</code></p> |
| <p><strong>References:</strong></p> |
| <ul> |
| <li><a href="https://issues.apache.org/jira/browse/SOLR-13971">https://issues.apache.org/jira/browse/SOLR-13971</a></li> |
| <li><a href="https://issues.apache.org/jira/browse/SOLR-14025">https://issues.apache.org/jira/browse/SOLR-14025</a></li> |
| <li><a href="https://cwiki.apache.org/confluence/display/SOLR/SolrSecurity">https://cwiki.apache.org/confluence/display/SOLR/SolrSecurity</a></li> |
| </ul> |
| <hr/> |
| <h1 id="cve-reports-for-apache-solr-dependencies">CVE reports for Apache Solr dependencies</h1> |
| <p>Below is a list of CVE vulnerabilities in Apache Solr dependencies, and the state of their applicability to Solr.</p> |
| <p>We are currently experimenting with providing this information in a <a href="#vex">machine-readable VEX format</a> and encourage you to participate.</p> |
| <table> |
| <tr> |
| <th>id</th> |
| <th>versions</th> |
| <th>jars</th> |
| <th>state</th> |
| <th>detail</th> |
| </tr> |
| <tr> |
| <td> |
| <a href="https://nvd.nist.gov/vuln/detail/CVE-2022-33980">CVE-2022-33980</a> </td> |
| <td> |
| < 9.1 |
| </td> |
| <td> |
| commons-configuration2-2.7.jar </td> |
| <td>not affected</td> |
| <td>Solr uses commons-configuration2 for "hadoop-auth" only (for Kerberos). It is only used for loading Hadoop configuration files that would only ever be provided by trusted administrators, not externally (untrusted).</td> |
| </tr> |
| <tr> |
| <td> |
| <a href="https://nvd.nist.gov/vuln/detail/CVE-2022-42889">CVE-2022-42889</a> </td> |
| <td> |
| < 9.1 |
| </td> |
| <td> |
| commons-text-1.9.jar </td> |
| <td>not affected</td> |
| <td>Solr uses commons-text directly (StringEscapeUtils.escapeEcmaScript) in LoadAdminUiServlet that is not vulnerable. Solr also has a "hadoop-auth" module that uses Apache Hadoop which uses commons-text through commons-configuration2. For Solr, the concern is limited to loading Hadoop configuration files that would only ever be provided by trusted administrators, not externally (untrusted).</td> |
| </tr> |
| <tr> |
| <td> |
| <a href="https://nvd.nist.gov/vuln/detail/CVE-2022-25168">CVE-2022-25168</a> </td> |
| <td> |
| < 9.1 |
| </td> |
| <td> |
| hadoop-common-3.2.2.jar </td> |
| <td>not affected</td> |
| <td>The vulnerable code won't be used by Solr because Solr only is only using HDFS as a client.</td> |
| </tr> |
| <tr> |
| <td> |
| <a href="https://nvd.nist.gov/vuln/detail/CVE-2021-44832">CVE-2021-44832</a> </td> |
| <td> |
| 7.4-8.11.1 |
| </td> |
| <td> |
| log4j-core-2.14.1.jar, log4j-core-2.16.0.jar </td> |
| <td>not affected</td> |
| <td>Solr's default log configuration doesn't use JDBCAppender and we don't imagine a user would want to use it or other obscure appenders.</td> |
| </tr> |
| <tr> |
| <td> |
| <a href="https://nvd.nist.gov/vuln/detail/CVE-2021-45105">CVE-2021-45105</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2021-45046">CVE-2021-45046</a> </td> |
| <td> |
| 7.4-8.11.1 |
| </td> |
| <td> |
| log4j-core-2.14.1.jar, log4j-core-2.16.0.jar </td> |
| <td>not affected</td> |
| <td>The MDC data used by Solr are for the collection, shard, replica, core and node names, and a potential trace id, which are all sanitized. Furthermore, Solr's default log configuration doesn't use double-dollar-sign and we don't imagine a user would want to do that.</td> |
| </tr> |
| <tr> |
| <td> |
| <a href="https://nvd.nist.gov/vuln/detail/CVE-2020-13955">CVE-2020-13955</a> </td> |
| <td> |
| 8.1.0- today |
| </td> |
| <td> |
| avatica-core-1.13.0.jar, calcite-core-1.18.0.jar </td> |
| <td>not affected</td> |
| <td>Solr's SQL adapter does not use the vulnerable class "HttpUtils". Calcite only used it to talk to Druid or Splunk.</td> |
| </tr> |
| <tr> |
| <td> |
| <a href="https://nvd.nist.gov/vuln/detail/CVE-2018-10237">CVE-2018-10237</a> </td> |
| <td> |
| 5.4.0-today |
| </td> |
| <td> |
| carrot2-guava-18.0.jar </td> |
| <td>not affected</td> |
| <td>Only used with the Carrot2 clustering engine.</td> |
| </tr> |
| <tr> |
| <td> |
| <a href="https://nvd.nist.gov/vuln/detail/CVE-2014-0114">CVE-2014-0114</a> </td> |
| <td> |
| 4.9.0-7.5.0 |
| </td> |
| <td> |
| commons-beanutils-1.8.3.jar </td> |
| <td>not affected</td> |
| <td>This is only used at compile time and it cannot be used to attack Solr. Since it is generally unnecessary, the dependency has been removed as of 7.5.0. See SOLR-12617.</td> |
| </tr> |
| <tr> |
| <td> |
| <a href="https://nvd.nist.gov/vuln/detail/CVE-2019-10086">CVE-2019-10086</a> </td> |
| <td> |
| 8.0.0-8.3.0 |
| </td> |
| <td> |
| commons-beanutils-1.9.3.jar </td> |
| <td>not affected</td> |
| <td>While commons-beanutils was removed in 7.5, it was added back in 8.0 in error and removed again in 8.3. The vulnerable class was not used in any Solr code path. This jar remains a dependency of both Velocity and hadoop-common, but Solr does not use it in our implementations.</td> |
| </tr> |
| <tr> |
| <td> |
| <a href="https://nvd.nist.gov/vuln/detail/CVE-2012-2098">CVE-2012-2098</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2018-1324">CVE-2018-1324</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2018-11771">CVE-2018-11771</a> </td> |
| <td> |
| 4.6.0-today |
| </td> |
| <td> |
| commons-compress (only as part of Ant 1.8.2) </td> |
| <td>not affected</td> |
| <td>Only used in test framework and at build time.</td> |
| </tr> |
| <tr> |
| <td> |
| <a href="https://nvd.nist.gov/vuln/detail/CVE-2018-1000632">CVE-2018-1000632</a> </td> |
| <td> |
| 4.6.0-today |
| </td> |
| <td> |
| dom4j-1.6.1.jar </td> |
| <td>not affected</td> |
| <td>Only used in Solr tests.</td> |
| </tr> |
| <tr> |
| <td> |
| <a href="https://nvd.nist.gov/vuln/detail/CVE-2018-10237">CVE-2018-10237</a> </td> |
| <td> |
| 4.6.0-today |
| </td> |
| <td> |
| guava-*.jar </td> |
| <td>not affected</td> |
| <td>Only used in tests.</td> |
| </tr> |
| <tr> |
| <td> |
| <a href="https://nvd.nist.gov/vuln/detail/CVE-2017-15718">CVE-2017-15718</a> </td> |
| <td> |
| 6.6.1-7.6.0 |
| </td> |
| <td> |
| hadoop-auth-2.7.4.jar, hadoop-hdfs-2.7.4.jar (all Hadoop) </td> |
| <td>not affected</td> |
| <td>Does not impact Solr because Solr uses Hadoop as a client library.</td> |
| </tr> |
| <tr> |
| <td> |
| <a href="https://nvd.nist.gov/vuln/detail/CVE-2017-14952">CVE-2017-14952</a> </td> |
| <td> |
| 6.0.0-7.5.0 |
| </td> |
| <td> |
| icu4j-56.1.jar, icu4j-59.1.jar </td> |
| <td>not affected</td> |
| <td>Issue applies only to the C++ release of ICU and not ICU4J, which is what Lucene uses. ICU4J is at v63.2 as of Lucene/Solr 7.6.0</td> |
| </tr> |
| <tr> |
| <td> |
| <a href="https://nvd.nist.gov/vuln/detail/CVE-2017-15095">CVE-2017-15095</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2017-17485">CVE-2017-17485</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2017-7525">CVE-2017-7525</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2018-5968">CVE-2018-5968</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2018-7489">CVE-2018-7489</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2019-12086">CVE-2019-12086</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2019-12384">CVE-2019-12384</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2018-12814">CVE-2018-12814</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2019-14379">CVE-2019-14379</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2019-14439">CVE-2019-14439</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2020-35490">CVE-2020-35490</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2020-35491">CVE-2020-35491</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2021-20190">CVE-2021-20190</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2019-14540">CVE-2019-14540</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2019-16335">CVE-2019-16335</a> </td> |
| <td> |
| 4.7.0-today |
| </td> |
| <td> |
| jackson-databind-*.jar </td> |
| <td>not affected</td> |
| <td>These CVEs, and most of the known jackson-databind CVEs since 2017, are all related to problematic 'gadgets' that could be exploited during deserialization of untrusted data. The Jackson developers described 4 conditions that must be met in order for a problematic gadget to be exploited. See <a href="https://medium.com/@cowtowncoder/on-jackson-cves-dont-panic-here-is-what-you-need-to-know-54cd0d6e8062">https://medium.com/@cowtowncoder/on-jackson-cves-dont-panic-here-is-what-you-need-to-know-54cd0d6e8062</a>. Solr's use of jackson-databind does not meet 1 of the 4 conditions described which makes these CVEs unexploitable. The specific condition that Solr does not meet is the 3rd one: 'Enable polymorphic type handling' Solr does not include any polymorphic type handling, and Solr does not configure jackson-databind de/serialization to expect or include class names in serialized JSON. Two CVEs, 2019-14540 & 2019-16335, are related to HikariConfig and HikariDataSource classes, neither of which are used in Solr's code base.</td> |
| </tr> |
| <tr> |
| <td> |
| <a href="https://nvd.nist.gov/vuln/detail/CVE-2019-10241">CVE-2019-10241</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2019-10247">CVE-2019-10247</a> </td> |
| <td> |
| 7.7.0-8.2 |
| </td> |
| <td> |
| jetty-9.4.14 </td> |
| <td>not affected</td> |
| <td>Solr upgraded to Jetty 9.4.19 for the 8.2 release. Additionally, the path to exploit these vulnerabilities was fixed in 8.1 and 7.7.2. Earlier versions can manually patch their configurations as described in SOLR-13409.</td> |
| </tr> |
| <tr> |
| <td> |
| <a href="https://nvd.nist.gov/vuln/detail/CVE-2020-27218">CVE-2020-27218</a> </td> |
| <td> |
| 7.3.0-8.8.0 |
| </td> |
| <td> |
| jetty-9.4.0 to 9.4.34 </td> |
| <td>not affected</td> |
| <td>Only exploitable through use of Jetty's GzipHandler, which is only implemented in Embedded Solr Server.</td> |
| </tr> |
| <tr> |
| <td> |
| <a href="https://nvd.nist.gov/vuln/detail/CVE-2020-27223">CVE-2020-27223</a> </td> |
| <td> |
| 7.3.0-present |
| </td> |
| <td> |
| jetty-9.4.6 to 9.4.36 </td> |
| <td>not affected</td> |
| <td>Only exploitable if Solr's webapp directory is deployed as a symlink, which is not Solr's default.</td> |
| </tr> |
| <tr> |
| <td> |
| <a href="https://nvd.nist.gov/vuln/detail/CVE-2021-33813">CVE-2021-33813</a> </td> |
| <td> |
| to present |
| </td> |
| <td> |
| jdom-*.jar </td> |
| <td>not affected</td> |
| <td>JDOM is only used in Solr Cell, which should not be used in production which makes the vulnerability unexploitable. It is a dependency of Apache Tika, which has analyzed the issue and determined the vulnerability is limited to two libraries not commonly used in search applications, see TIKA-3488 for details. Since Tika should be used outside of Solr, use a version of Tika which updates the affected libraries if concerned about exposure to this issue.</td> |
| </tr> |
| <tr> |
| <td> |
| <a href="https://nvd.nist.gov/vuln/detail/CVE-2018-1000056">CVE-2018-1000056</a> </td> |
| <td> |
| 4.6.0-7.6.0 |
| </td> |
| <td> |
| junit-4.10.jar </td> |
| <td>not affected</td> |
| <td>JUnit only used in tests; CVE only refers to a Jenkins plugin not used by Solr.</td> |
| </tr> |
| <tr> |
| <td> |
| <a href="https://nvd.nist.gov/vuln/detail/CVE-2014-7940">CVE-2014-7940</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2016-6293">CVE-2016-6293</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2016-7415">CVE-2016-7415</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2017-14952">CVE-2017-14952</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2017-17484">CVE-2017-17484</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2017-7867">CVE-2017-7867</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2017-7868">CVE-2017-7868</a> </td> |
| <td> |
| 7.3.1 |
| </td> |
| <td> |
| lucene-analyzers-icu-7.3.1.jar </td> |
| <td>not affected</td> |
| <td>All of these issues apply to the C++ release of ICU and not ICU4J, which is what Lucene uses.</td> |
| </tr> |
| <tr> |
| <td> |
| <a href="https://nvd.nist.gov/vuln/detail/CVE-2019-16869">CVE-2019-16869</a> </td> |
| <td> |
| 8.2-8.3 |
| </td> |
| <td> |
| netty-all-4.1.29.Final.jar </td> |
| <td>not affected</td> |
| <td>This is not included in Solr but is a dependency of ZooKeeper 3.5.5. The version was upgraded in ZooKeeper 3.5.6, included with Solr 8.3. The specific classes mentioned in the CVE are not used in Solr (nor in ZooKeeper as far as the Solr community can determine).</td> |
| </tr> |
| <tr> |
| <td> |
| <a href="https://nvd.nist.gov/vuln/detail/CVE-2017-14868">CVE-2017-14868</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2017-14949">CVE-2017-14949</a> </td> |
| <td> |
| 5.2.0-today |
| </td> |
| <td> |
| org.restlet-2.3.0.jar </td> |
| <td>not affected</td> |
| <td>Solr should not be exposed outside a firewall where bad actors can send HTTP requests. These two CVEs specifically involve classes (SimpleXMLProvider and XmlRepresentation, respectively) that Solr does not use in any code path.</td> |
| </tr> |
| <tr> |
| <td> |
| <a href="https://nvd.nist.gov/vuln/detail/CVE-2015-5237">CVE-2015-5237</a> </td> |
| <td> |
| 6.5.0-today |
| </td> |
| <td> |
| protobuf-java-3.1.0.jar </td> |
| <td>not affected</td> |
| <td>Dependency for Hadoop and Calcite. ??</td> |
| </tr> |
| <tr> |
| <td> |
| <a href="https://nvd.nist.gov/vuln/detail/CVE-2018-1471">CVE-2018-1471</a> </td> |
| <td> |
| 5.4.0-7.7.2, 8.0-8.3 |
| </td> |
| <td> |
| simple-xml-2.7.1.jar </td> |
| <td>not affected</td> |
| <td>Dependency of Carrot2 and used during compilation, not at runtime (see SOLR-769. This .jar was replaced in Solr 8.3 and backported to 7.7.3 (see SOLR-13779).</td> |
| </tr> |
| <tr> |
| <td> |
| <a href="https://nvd.nist.gov/vuln/detail/CVE-2018-8088">CVE-2018-8088</a> </td> |
| <td> |
| 4.x-today |
| </td> |
| <td> |
| slf4j-api-1.7.24.jar, jcl-over-slf4j-1.7.24.jar, jul-to-slf4j-1.7.24.jar </td> |
| <td>not affected</td> |
| <td>The reported CVE impacts org.slf4j.ext.EventData, which is not used in Solr.</td> |
| </tr> |
| <tr> |
| <td> |
| <a href="https://nvd.nist.gov/vuln/detail/CVE-2018-1335">CVE-2018-1335</a> </td> |
| <td> |
| 7.3.1-7.5.0 |
| </td> |
| <td> |
| tika-core.1.17.jar </td> |
| <td>not affected</td> |
| <td>Solr does not run tika-server, so this is not a problem.</td> |
| </tr> |
| <tr> |
| <td> |
| <a href="https://nvd.nist.gov/vuln/detail/CVE-">CVE-</a> </td> |
| <td> |
| 7.3.1-today |
| </td> |
| <td> |
| tika-core.*.jar </td> |
| <td>not affected</td> |
| <td>All Tika issues that could be Solr vulnerabilities would only be exploitable if untrusted files are indexed with SolrCell. This is not recommended in production systems, so Solr does not consider these valid CVEs for Solr.</td> |
| </tr> |
| <tr> |
| <td> |
| <a href="https://nvd.nist.gov/vuln/detail/CVE-">CVE-</a> </td> |
| <td> |
| 6.6.2-today |
| </td> |
| <td> |
| velocity-tools-2.0.jar </td> |
| <td>not affected</td> |
| <td>Solr does not ship a Struts jar. This is a transitive POM listing and not included with Solr (see comment in SOLR-2849).</td> |
| </tr> |
| <tr> |
| <td> |
| <a href="https://nvd.nist.gov/vuln/detail/CVE-2016-6809">CVE-2016-6809</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2018-1335">CVE-2018-1335</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2018-1338">CVE-2018-1338</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2018-1339">CVE-2018-1339</a> </td> |
| <td> |
| 5.5.5, 6.2.0-today |
| </td> |
| <td> |
| vorbis-java-tika-0.8.jar </td> |
| <td>not affected</td> |
| <td>See <a href="https://github.com/Gagravarr/VorbisJava/issues/30">https://github.com/Gagravarr/VorbisJava/issues/30</a>; reported CVEs are not related to OggVorbis at all.</td> |
| </tr> |
| <tr> |
| <td> |
| <a href="https://nvd.nist.gov/vuln/detail/CVE-2012-0881">CVE-2012-0881</a> </td> |
| <td> |
| ~2.9-today |
| </td> |
| <td> |
| xercesImpl-2.9.1.jar </td> |
| <td>not affected</td> |
| <td>Only used in Lucene Benchmarks and Solr tests.</td> |
| </tr> |
| </table> |
| </div> |
| </div> |
| </div> |
| <footer> |
| <div class="row"> |
| <div class="small-6 medium-3 columns"> |
| <h4>Features</h4> |
| <ul> |
| <li><a href="/features.html">Overview</a></li> |
| <li><a href="/features.html#data-handling">Data Handling</a></li> |
| <li><a href="/features.html#query">Querying</a></li> |
| <li><a href="/features.html#facets">Faceting</a></li> |
| <li><a href="/features.html#discovery">Discovery</a></li> |
| <li><a href="/features.html#plugins">Plugins and Extensions</a></li> |
| <li><a href="/features.html#stats">Statistics and Aggregations</a></li> |
| <li><a href="/features.html#spatial">Spatial</a></li> |
| <li><a href="/features.html#rich-content">Rich Content</a></li> |
| <li><a href="/features.html#performance">Performance</a></li> |
| <li><a href="/features.html#solrcloud">Scaling with SolrCloud</a></li> |
| <li><a href="/features.html#admin-ui">User Interface</a></li> |
| </ul> |
| </div> |
| <div class="small-6 medium-3 columns"> |
| <h4>Resources</h4> |
| <ul> |
| <li><a href="/resources.html#tutorials">Tutorial</a></li> |
| <li><a href="/resources.html#documentation">Docs</a></li> |
| <li><a href="/resources.html#solr-books">Books</a></li> |
| <li><a href="/resources.html#presentations">Presentations</a></li> |
| <li><a href="/resources.html#videos">Videos</a></li> |
| <li><a href="/logos-and-assets.html">Solr Logos and Assets</a></li> |
| <li><a href="/editing-website.html">Editing this Website</a></li> |
| <br/> |
| <li><a href="https://www.apache.org/">Apache Software Foundation</a></li> |
| <li><a href="https://www.apache.org/foundation/thanks.html">Thanks</a></li> |
| <li><a href="https://www.apache.org/foundation/sponsorship.html">Sponsorship</a></li> |
| <li><a href="https://www.apache.org/security/">Security</a></li> |
| <li><a href="https://www.apache.org/licenses/">License</a></li> |
| </ul> |
| </div> |
| <div class="small-6 medium-3 columns"> |
| <h4>Get Started</h4> |
| <ul> |
| <li><a href="/downloads.html">Download</a></li> |
| <li><a href="/guide/solr-tutorial.html">Run Through the Tutorial</a></li> |
| <li><a href="/resources.html">Level Up</a></li> |
| </ul> |
| <br/> |
| <h4>Community</h4> |
| <ul> |
| <li><a href="/community.html#support">Support</a></li> |
| <li><a href="/community.html#mailing-lists-irc">Mailing Lists</a></li> |
| <li><a href="/community.html#issue-tracker">Issues (JIRA)</a></li> |
| <li><a href="/community.html#how-to-contribute">Contribute</a></li> |
| <li><a href="/community.html#version-control">Version control (GIT)</a></li> |
| </ul> |
| </div> |
| <div class="small-6 medium-3 columns"> |
| <h4>Related Projects</h4> |
| <ul> |
| <li><a href="http://lucene.apache.org/">Apache Lucene</a></li> |
| <li><a href="http://zookeeper.apache.org/">Apache Zookeeper</a></li> |
| <li><a href="http://tika.apache.org/">Apache Tika</a></li> |
| <li><a href="http://manifoldcf.apache.org/">Apache ManifoldCF</a></li> |
| <li><a href="http://spark.apache.org/">Apache Spark</a></li> |
| <li><a href="http://nutch.apache.org/">Apache Nutch</a></li> |
| <li><a href="http://zeppelin.apache.org/">Apache Zeppelin</a></li> |
| <li><a href="http://opennlp.apache.org/">Apache OpenNLP</a></li> |
| </ul> |
| </div> |
| </div> |
| <div class="row copyright"> |
| <div class="large-centered columns"> |
| <p>Copyright © 2024 The Apache Software Foundation, Licensed under the |
| <a href="https://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>. <a href="https://privacy.apache.org/policies/privacy-policy-public.html">Privacy Policy</a><br/> |
| Apache and the Apache feather logo are trademarks of The Apache Software Foundation. Apache Lucene, |
| Apache Solr and their respective logos are trademarks of the Apache Software Foundation. |
| Please see the <a href="https://www.apache.org/foundation/marks/">Apache Trademark Policy</a> for more information. |
| All non-Apache logos are the trademarks of their respective owners.</p> |
| </div></div> </footer> |
| |
| <script> |
| $(document).foundation(); |
| </script> |
| <script> |
| $(document).ready(function(){ |
| $('.slider').slick({ |
| infinite: false, |
| speed: 300, |
| slidesToShow: 6, |
| slidesToScroll: 6, |
| responsive: [ |
| { |
| breakpoint: 1024, |
| settings: { |
| slidesToShow: 4, |
| slidesToScroll: 4, |
| infinite: true |
| } |
| }, |
| { |
| breakpoint: 600, |
| settings: { |
| slidesToShow: 3, |
| slidesToScroll: 3 |
| } |
| }, |
| { |
| breakpoint: 480, |
| settings: { |
| slidesToShow: 2, |
| slidesToScroll: 2 |
| } |
| }, |
| { |
| breakpoint: 320, |
| settings: { |
| slidesToShow: 1, |
| slidesToScroll: 1 |
| } |
| } |
| ], |
| prevArrow: '<i class="fa fa-angle-left fa-2x slider-prev"></i>', |
| nextArrow: '<i class="fa fa-angle-right fa-2x slider-next"></i>' |
| }); |
| }); |
| </script> </body> |
| </html> |
