Skip to content

Issue in Anomaly Detection with document and field level rules in numerical feature aggregations

Moderate
CEHENKLE published GHSA-47qw-jwpx-pp4c Feb 2, 2023

Package

docker OpenSearch (Docker)

Affected versions

<1.3.8, <2.6.0

Patched versions

>=1.3.8, >=2.6.0

Description

Affected versions

OpenSearch 1.0.0-1.3.7 and 2.0.0-2.5.0

Patched versions

OpenSearch 1.3.8 and 2.6.0

Impact

There is an issue with the application of document and field level restrictions in the Anomaly Detection plugin, where users with the Anomaly Detector role can read aggregated numerical data (e.g. averages, sums) of fields that are otherwise restricted to them.

This issue only affects authenticated users who were previously granted read access to the indexes containing the restricted fields.

Workarounds

There are no known workarounds for this issue.

Patches

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

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 [email protected]. Please do not create a public GitHub issue.

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.0/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N

CVE ID

CVE-2023-23933

Weaknesses

No CWEs