Summaryinfo

A vulnerability labeled as problematic has been found in OpenSearch. This affects an unknown part of the component Java Security Manager Policy Configuration. Such manipulation leads to information disclosure. This vulnerability is documented as CVE-2022-41917. The attack can be executed remotely. There is not any exploit available. The affected component should be upgraded. If you want to get best quality of vulnerability data, you may have to visit VulDB.

Detailsinfo

A vulnerability was found in OpenSearch. It has been rated as problematic. Affected by this issue is an unknown part of the component Java Security Manager Policy Configuration. The manipulation with an unknown input leads to a information disclosure vulnerability. Using CWE to declare the problem leads to CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Impacted is confidentiality. CVE summarizes:

OpenSearch is a community-driven, open source fork of Elasticsearch and Kibana. OpenSearch allows users to specify a local file when defining text analyzers to process data for text analysis. An issue in the implementation of this feature allows certain specially crafted queries to return a response containing the first line of text from arbitrary files. The list of potentially impacted files is limited to text files with read permissions allowed in the Java Security Manager policy configuration. OpenSearch version 1.3.7 and 2.4.0 contain a fix for this issue. Users are advised to upgrade. There are no known workarounds for this issue.

The weakness was released 11/16/2022 as GHSA-w3rx-m34v-wrqx. The advisory is shared for download at github.com. This vulnerability is handled as CVE-2022-41917 since 09/30/2022. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1592.

Upgrading to version 1.3.7 or 2.4.0 eliminates this vulnerability. Applying the patch 6d20423f5920745463b1abc5f1daf6a786c41aa0 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Name

• OpenSearch

License

• open-source

CPE 2.3info

• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Discussion