# CVE-2022-41918: Issue with fine-grained access control of indices backing data streams > Attackers can bypass fine-grained access controls on data stream indices, potentially reading unauthorized data in OpenSearch deployments. - **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 15 Nov 2022 - **Updated:** 23 Apr 2025 - **Also known as:** GHSA-wmx7-x4jp-9jgg ## What is CVE-2022-41918? CVE-2022-41918 is a medium-severity missing authorization vulnerability in opensearch-project security, published on 15 Nov 2022. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description OpenSearch is a community-driven, open source fork of Elasticsearch and Kibana. There is an issue with the implementation of fine-grained access control rules (document-level security, field-level security and field masking) where they are not correctly applied to the indices that back data streams potentially leading to incorrect access authorization. OpenSearch 1.3.7 and 2.4.0 contain a fix for this issue. Users are advised to update. There are no known workarounds for this issue. Weakness: CWE-863 (Incorrect Authorization), CWE-612 (Improper Authorization of Index Containing Sensitive Information) ## Which versions are affected by CVE-2022-41918? 4 open source packages ship an affected version, including org.opensearch.plugin:opensearch-security. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.opensearch.plugin:opensearch-security` | Maven | All versions | 1.3.7 | | `org.opensearch.plugin:opensearch-security` | Maven | All versions | 1.3.7 | | `org.opensearch.plugin:opensearch-security` | Maven | From 2.0.0 | 2.4.0 | | `org.opensearch.plugin:opensearch-security` | Maven | From 2.0.0 | 2.4.0 | Products: Amazon Opensearch. ## How do I fix CVE-2022-41918? Upgrade org.opensearch.plugin:opensearch-security to a fixed version for your release line: 1.3.7 or 2.4.0. ## Is CVE-2022-41918 being exploited? There is no known exploitation of CVE-2022-41918 in the wild and no public exploit code. ## Other vulnerabilities in opensearch-project security - [CVE-2022-31115](https://insights.sbomify.com/CVE-2022-31115/): Unsafe YAML deserialization in opensearch-ruby (high 8.8) - [CVE-2025-9624](https://insights.sbomify.com/CVE-2025-9624/): OpenSearch 3.2.0 - Nested Boolean/Disjunction asymmetric DoS (high 8.3) - [CVE-2022-35980](https://insights.sbomify.com/CVE-2022-35980/): OpenSearch vulnerable to Improper Authorization of Index Containing Sensitive Information (high 7.5) - [CVE-2023-23933](https://insights.sbomify.com/CVE-2023-23933/): Issue in Anomaly Detection with document and field level rules in numerical feature aggregations (medium 5.7) - [CVE-2023-23613](https://insights.sbomify.com/CVE-2023-23613/): Field-level security issue with .keyword fields in OpenSearch (medium 5.7) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2022-41918 and fix it if it is affected. What it is: CVE-2022-41918 is a medium-severity missing authorization vulnerability in opensearch-project security, published on 15 Nov 2022. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2022-41918 in the wild and no public exploit code. Affected packages and fixed versions: - org.opensearch.plugin:opensearch-security (Maven): affected all versions; fixed in 1.3.7 - org.opensearch.plugin:opensearch-security (Maven): affected all versions; fixed in 1.3.7 - org.opensearch.plugin:opensearch-security (Maven): affected from 2.0.0; fixed in 2.4.0 - org.opensearch.plugin:opensearch-security (Maven): affected from 2.0.0; fixed in 2.4.0 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2022-41918/ (Markdown: https://insights.sbomify.com/CVE-2022-41918/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2022-41918 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-41918 - OSV: https://osv.dev/vulnerability/CVE-2022-41918 --- From sbomify Insights: https://insights.sbomify.com/CVE-2022-41918/ Summaries are generated and may contain mistakes; the official description above is the record.