Security
Headlines
HeadlinesLatestCVEs

Headline

GHSA-977c-63xq-cgw3: Unsafe YAML deserialization in opensearch-ruby

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

https://github.com/opensearch-project/opensearch-ruby/pull/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:

ghsa
#git#ruby

Package

bundler opensearch-ruby (RubyGems)

Affected versions

< 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:

  • Open an issue in opensearch-ruby

References

  • GHSA-977c-63xq-cgw3
  • https://nvd.nist.gov/vuln/detail/CVE-2022-31115
  • opensearch-project/opensearch-ruby#77
  • https://staaldraad.github.io/post/2021-01-09-universal-rce-ruby-yaml-load-updated/

CEHENKLE published the maintainer security advisory

Jun 30, 2022

Related news

CVE-2022-31115

opensearch-ruby is a community-driven, open source fork of elasticsearch-ruby. In versions prior to 2.0.1 the ruby `YAML.load` function was used instead of `YAML.safe_load`. As a result opensearch-ruby 2.0.0 and prior can lead to unsafe deserialization using YAML.load if the response is of type YAML. An attacker must be in control of an opensearch server and convince the victim to connect to it in order to exploit this vulnerability. The problem has been patched in opensearch-ruby gem version 2.0.1. Users are advised to upgrade. There are no known workarounds for this issue.