3/6/2023 0 Comments Apache lucene cve![]() ![]() This advisory is only used to describe a potential risk. Ensure that network settings are configured so that only trusted traffic communicates with Solr, especially to the DIH request handler.Users can edit solrconfig.xml to configure all DataImportHandler usages with an “invariants” section listing the “dataConfig” parameter set to an empty string.Users can upgrade Solr to 8.2.0 or later to protect against this vulnerability: Starting with Solr 8.2.0, the use of the dataConfig parameter requires setting the Java system property “” to “true”. If the current version is affected and lacks the related protection configuration, this version is vulnerable and users are advised to take protection measures as soon as possible. User can check the current Solr version on the Solr administration dashboard. Users of this software are advised to upgrade Apache Solr to a secure version to protect against this vulnerability. As a DIH configuration can contain scripts, this parameter is a security risk.Īn attacker could exploit this vulnerability to cause arbitrary code execution via a malicious request that contains a carefully crafted dataConfig parameter. The whole DIH configuration of this module can come from the dataConfig parameter included in an external request. This vulnerability exists in the DataImportHandler module, a common module used to import data from databases or other sources. Get a free 30-day trial of Tenable.io Vulnerability Management.Recently, Apache Software Foundation (ASF) issued a security bulletin to announce the fix of the remote arbitrary code execution vulnerability (CVE-2019-0193) in Apache Solr. ![]() ![]() Learn more about Tenable, the first Cyber Exposure platform for holistic management of your modern attack surface. Join Tenable's Security Response Team on the Tenable Community. jas502n's Exploit Script for Apache Solr RCE (Velocity Template).s00py’s GitHub Gist for Apache Solr RCE (Velocity Template).According to the advisory, “Solr 8.4 removed the params resource loader entirely, and only enables the configset-provided template rendering when the configset is `trusted` (has been uploaded by an authenticated user).” Identifying affected systemsĪ list of Tenable plugins to identify this vulnerability will appear here as they’re released. However, following the release of 8.3.1, researcher Peter Cseh of Cloudera reported the fix as incomplete to the Apache Solr team, resulting in the hardening of VelocityResponseWriter as part of Solr version 8.4. On December 3, Apache released Solr version 8.3.1, which reportedly addressed CVE-2019-17558 as referenced in SOLR-13971. Days later, an exploit script was published to a GitHub repository. Proof of conceptĪs mentioned previously, a PoC was published on October 29 as a Github Gist. Once the core names have been identified, an attacker can send a specially crafted HTTP POST request to the Config API to toggle the params resource loader value for the Velocity Response Writer in the solrconfig.xml file to true.Įnabling this parameter would allow an attacker to use the velocity template parameter in a specially crafted Solr request, leading to RCE.ĭespite the recent release of Apache Solr 8.3 that addresses a default configuration flaw that was reported back in July, this flaw remained a zero-day until December 29. AnalysisĪccording to the PoC, an attacker could target a vulnerable Apache Solr instance by first identifying a list of Solr core names. After the announcement from Apache was released, we can now confirm versions 5.0.0 to 8.3.1 are affected. Tenable Research confirmed that Apache Solr versions 7.7.2 through 8.3 were vulnerable at the time this blog post was originally published. At the time this blog post was published, this vulnerability did not have a CVE identifier and no confirmation or indication of a solution available from Apache. However, Apache recently announced releases of Solr to address this vulnerability, which is now identified as CVE-2019-17558. On October 29, a proof of concept (PoC) for a remote code execution (RCE) vulnerability in Apache Solr, a popular open-source search platform built on Apache Lucene, was published as a GitHub Gist. UPDATE : The background and solution sections below have been updated to reflect the recent security update released by Apache. Apache Solr remained vulnerable to a zero-day weeks after proof-of-concept code became public for CVE-2019-17558. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |