Skip to content

OpenSearch vulnerable to Improper Authorization of Index Containing Sensitive Information

High severity GitHub Reviewed Published Aug 12, 2022 in opensearch-project/security • Updated Feb 1, 2023

Package

maven org.opensearch.plugin:opensearch-security (Maven)

Affected versions

>= 2.0.0.0, <= 2.1.0.0

Patched versions

2.2.0.0

Description

Impact

Requests to an OpenSearch cluster configured with advanced access control features (document level security (DLS), field level security (FLS), and/or field masking) will not be filtered when the query's search pattern matches an aliased index.

OpenSearch Dashboards creates an alias to .kibana by default, so filters with the index pattern of * to restrict access to documents or fields will not be applied.

This issue allows requests to access sensitive information when customer have acted to restrict access that specific information.

Patches

OpenSearch 2.2.0+ contains the fix for this issue. OpenSearch Security Plugin 2.2.0.0 is compatible with OpenSearch 2.2.0.

Workarounds

There is no recommended work around.

References

See pull request #1999 for additional details.

For more information

If you have any questions or comments about this advisory we ask that contact AWS/Amazon Security via our vulnerability reporting page or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue.

References

@peternied peternied published to opensearch-project/security Aug 12, 2022
Published to the GitHub Advisory Database Aug 12, 2022
Reviewed Aug 12, 2022
Published by the National Vulnerability Database Aug 12, 2022
Last updated Feb 1, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS score

0.099%
(42nd percentile)

Weaknesses

CVE ID

CVE-2022-35980

GHSA ID

GHSA-f4qr-f4xx-hjxw

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.