Skip to content

opensearch-ruby 2.x before 2.0.2 vulnerable to unsafe YAML deserialization

High severity GitHub Reviewed Published Jun 30, 2022 in opensearch-project/opensearch-ruby • Updated Mar 31, 2023

Package

bundler opensearch-ruby (RubyGems)

Affected versions

>= 2.0.0, < 2.0.2

Patched versions

2.0.2

Description

Impact

A YAML deserialization in opensearch-ruby 2.0.0 can lead to unsafe deserialization using YAML.load if the response is of type YAML.

Patches

The problem has been patched in opensearch-ruby gem version 2.0.2.

Workarounds

No viable workaround. Please upgrade to 2.0.2

References

opensearch-project/opensearch-ruby#77
https://staaldraad.github.io/post/2021-01-09-universal-rce-ruby-yaml-load-updated/

For more information

If you have any questions or comments about this advisory:

References

@CEHENKLE CEHENKLE published to opensearch-project/opensearch-ruby Jun 30, 2022
Published by the National Vulnerability Database Jun 30, 2022
Published to the GitHub Advisory Database Jul 5, 2022
Reviewed Jul 5, 2022
Last updated Mar 31, 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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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:R/S:U/C:H/I:H/A:H

EPSS score

0.308%
(70th percentile)

Weaknesses

CVE ID

CVE-2022-31115

GHSA ID

GHSA-977c-63xq-cgw3

Source code

Credits

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