Skip to content

OpenSearch unauthorized data access on fields protected by field level security if field is a member of an object

Moderate severity GitHub Reviewed Published Aug 1, 2025 in opensearch-project/security • Updated Aug 1, 2025

Package

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

Affected versions

< 2.19.3.0

Patched versions

2.19.3.0

Description

Impact

OpenSearch versions 2.19.2 and earlier improperly apply Field Level Security (FLS) rules on fields which are not at the top level of the source document tree (i.e., which are members of a JSON object).

If an FLS exclusion rule (like ~object) is applied to an object valued attribute in a source document, the object is properly removed from the _source document in search and get results. However, any member attribute of that object remains available to search queries. This allows to reconstruct the original field contents using range queries.

Patches

The issue has been resolved in OpenSearch 3.0.0 and OpenSearch 2.19.3.

Workarounds

If FLS exclusion rules are used for object valued attributes (like ~object), add an additional exclusion rule for the members of the object (like ~object.*).

References

@cwperks cwperks published to opensearch-project/security Aug 1, 2025
Published to the GitHub Advisory Database Aug 1, 2025
Reviewed Aug 1, 2025
Last updated Aug 1, 2025

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

Weaknesses

Exposure of Sensitive Information to an Unauthorized Actor

The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Learn more on MITRE.

CVE ID

No known CVE

GHSA ID

GHSA-2rjv-cv85-xhgm

Source code

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