Skip to main content
Public proof of conceptFix available

CVE-2022-31115

A public proof of concept exists; no exploitation attested.

  • Published2022-06-30
  • Fixed in2.0.2
  • WeaknessCWE-502

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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.

Timeline

dates in UTC
  1. 2022-06-3022:15CVE publishedNVD

Versions per branch

NVD · OSV
Amazon opensearch
BranchAffectedFixed in
2.0< 2.0.22.0.2
2.0≥ 2.0.0, < 2.0.22.0.2

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As GitHub_M, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • opensearch-project opensearch-ruby
    Affected
    • = < 2.0.1no fix stated

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2022-06-30

Fix

  1. Update Amazon opensearch to 2.0.2

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

  • CISA-ADPSSVC decisionpoc2025-04-22
  • CNACVSS 3.18.8known since 2026-10-23
  • NVDCVSS 3.18.8read 2026-10-23
  • NVDCVSS 2.06.8read 2026-10-23
  • CNAweakness (CWE)CWE-502known since 2026-10-23
  • FIRST EPSSEPSS score1.6 %2026-11-08
  • OSVaffected packages—
  • GitHub AdvisoriesadvisoryHIGH2022-07-05

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Published
2022-06-30
Last Modified
2026-06-17
NVD status
Modified
GitHub Advisory
GHSA-977c-63xq-cgw3

Frequently asked questions

What is 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.

Is CVE-2022-31115 actively exploited?

A proof-of-concept exploit exists for CVE-2022-31115, but active exploitation has not been confirmed at this time.

What is the CVSS score for CVE-2022-31115?

CVE-2022-31115 has a CVSS v3 base score of 8.8 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H.

Running opensearch-ruby? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record