Skip to content

Field-level security issue with .keyword fields in OpenSearch

Moderate severity GitHub Reviewed Published Jan 24, 2023 in opensearch-project/security • Updated Mar 7, 2023

Package

maven org.opensearch:opensearch-security (Maven)

Affected versions

< 1.3.8
>= 2.0.0, < 2.5.0

Patched versions

1.3.8
2.5.0

Description

Advisory title: Field-level security issue with .keyword fields

Affected versions:

OpenSearch 1.0.0-1.3.7 and 2.0.0-2.4.1

Patched versions:

OpenSearch 1.3.8 and 2.5.0

Impact:

There is an issue in the implementation of field-level security (FLS) and field masking where rules written to explicitly exclude fields are not correctly applied for certain queries that rely on their auto-generated .keyword fields.

This issue is only present for authenticated users with read access to the indexes containing the restricted fields.

Workaround:

FLS rules that use explicit exclusions can be written to grant explicit access instead. Policies authored in this way are not subject to this issue.

Patches:

OpenSearch versions 1.3.8 and 2.5.0 contain a fix for this issue.

For more information:

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

References

@CEHENKLE CEHENKLE published to opensearch-project/security Jan 24, 2023
Published to the GitHub Advisory Database Jan 24, 2023
Reviewed Jan 24, 2023
Published by the National Vulnerability Database Jan 26, 2023
Last updated Mar 7, 2023

Severity

Moderate

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
Low
User interaction
Required
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:L/UI:R/S:U/C:H/I:N/A:N

EPSS score

0.063%
(28th percentile)

Weaknesses

CVE ID

CVE-2023-23613

GHSA ID

GHSA-v3cg-7r9h-r2g6

Source code

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