# What is CVE-2022-41918?

> CVE-2022-41918 is a medium-severity flaw (CVSS 6.3) in Opensearch from Amazon, published on 15 November 2022. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 0.4%. If you run an affected version, plan in the vendor’s fix.

Canonical page: https://www.edgeprotect.io/what-is/cve-2022-41918

## At a glance

- **Verdict:** Plan it in. No sign of exploitation and a low forecast. Patch it in your normal update cycle.
- **EdgeProtect risk score:** 29 out of 100 (Low); action: Monitor. Kept up to date as the evidence changes.
- **Severity:** Medium (CVSS 6.3 out of 10)
- **Known to be exploited:** No, not on the list of flaws known to be exploited today
- **Chance of use in the next 30 days:** 0.4% (latest exploit-likelihood forecast)
- **Published:** 15 November 2022
- **Record last updated:** 27 June 2023
- **Main product:** Opensearch from Amazon
- **Affected products:** 1

## What is CVE-2022-41918? In plain terms

It can be attacked from anywhere on the internet with an ordinary user account, and nobody has to click anything. If it works, the attacker can read some data, change some data and slow it down.

### The 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.

### What kind of flaw is it?

- CWE-863: Incorrect Authorization
- CWE-612: Improper Authorization of Index Containing Sensitive Information

### How an attack on it works

- Where an attacker can be: Anywhere on the internet
- How hard it is to pull off: Easy: no special conditions
- Login needed first: An ordinary user account
- Does someone have to click: No, nobody has to do anything
- What an attacker gets: Can read some data, change some data and slow it down

Severity vector: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`

## Is CVE-2022-41918 being exploited? Not that we know of

It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 0.4%. That can change at any time, which is why we keep watching.

Exploit likelihood over the last 7 days: 0.4%, 0.4%, 0.4%, 0.4%, 0.4%, 0.4%, 0.4%.

### Timeline

- 15 November 2022: Published
- 27 June 2023: Record last updated

### How EdgeProtect ranks it

CVE-2022-41918 scores **29 out of 100 (Low)**, with the action "Monitor".

Every published flaw gets a risk score from 0 to 100, kept up to date as the evidence changes. Four things go into the score, from the one that counts most to the ones that count less:

- Evidence it is being exploited: biggest factor
- How severe it is: strong factor
- How widely exposed it is: key context
- Real threat activity around it: key context

85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score. When this flaw matches software you track, it lands in your list with its score and the reasons behind it.

## Who is affected by CVE-2022-41918?

The published record lists 1 product. Versions are as published: "before 1.3.7" means every version up to, but not including, 1.3.7.

- [Opensearch](https://www.edgeprotect.io/product/amazon/opensearch) by [Amazon](https://www.edgeprotect.io/vendors/amazon) (Application): before 1.3.7, 2.0.0 to before 2.4.0

## How do I fix CVE-2022-41918?

1. **Check whether you run it.** Compare your versions with the affected products above. Not sure what you run? EdgeProtect can work it out from your public website, or you can pick it from a list.
2. **Apply the vendor’s fix.** Install the update named in the vendor’s advisory. We’ve put the advisory first in the list.
3. **If you can’t patch today.** Follow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
4. **Keep an eye on it.** Track the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood.

### References

- [github.com](https://github.com/opensearch-project/security/commit/f7cc569c9d3fa5d5432c76c854eed280d45ce6f4) (Patch, Third-party advisory)
- [github.com](https://github.com/opensearch-project/security/security/advisories/GHSA-wmx7-x4jp-9jgg) (Third-party advisory)

## Questions

### What is CVE-2022-41918?

CVE-2022-41918 is a medium-severity flaw in Opensearch from Amazon, published on 15 November 2022. It can be attacked from anywhere on the internet with an ordinary user account, and nobody has to click anything. If it works, the attacker can read some data, change some data and slow it down.

### How serious is CVE-2022-41918?

It scores 6.3 out of 10 on the CVSS severity scale, which is medium. Our risk score for CVE-2022-41918 is 29 out of 100, which is Low. Its action is "Monitor". No sign of exploitation and a low forecast. Patch it in your normal update cycle.

### Is CVE-2022-41918 being exploited?

It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 0.4%. That can change at any time, which is why we keep watching.

### Which versions does CVE-2022-41918 affect?

For Opensearch from Amazon: before 1.3.7, 2.0.0 to before 2.4.0.

### How do I fix CVE-2022-41918?

Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet.

## Does CVE-2022-41918 affect you?

EdgeProtect keeps checking for you:

- **Tell us what you run.** Pick your software from a list, or let us work it out from your website.
- **We match it to every flaw.** Over 400,000 published flaws, checked against your list.
- **Ranked by real-world risk.** Every flaw gets a 0 to 100 risk score, kept up to date, led by evidence criminals are using it.
- **Told as soon as we know.** An alert by email, in the app or by webhook to your own tools.

Start free (no card, nothing to install): https://www.edgeprotect.io/register
Book a demo: https://www.edgeprotect.io/contact