Skip to content
Fencer Intel
low 2.2

GHSA-22vx-2x23-98w6 json

OpenSearch vulnerable to improper authorization for Rollover Requests

published 6mo ago modified 6mo ago

cvss
2.2
version 3.1, GitHub
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

### Description

A flaw was identified in the OpenSearch Security plugin's handling of index rollover requests. When a rollover request included an explicit target index name, the security plugin did not properly evaluate access control permissions against the target index. This could allow a user with rollover permissions on a source index to create a new index with a name they are not authorized to use.

### Impact

A user with `indices:admin/rollover` permission on a source index pattern could roll over to a target index name outside their authorized index patterns. This is limited to index creation via the rollover API and requires the user to already have rollover privileges on the source index.

### Patches

This issue is fixed in OpenSearch 2.19.4 and 3.2.0

### Workarounds

Grant the `indices:admin/rollover` permission only to fully trusted users.

Patch / fix

  • maven org.opensearch.plugin:opensearch-security 2.19.4.0, 3.2.0.0

Is GHSA-22vx-2x23-98w6 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CVSS scores

assigned by version score vector
GitHub 3.1 2.2 CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:L/A:N

Affected packages

ecosystem package affected fixed in
maven org.opensearch.plugin:opensearch-security
>=1.0.0, <2.19.4.0
>=3.0.0, <3.2.0.0
2.19.4.0
3.2.0.0

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.