What is CVE-2022-31115?

CVE-2022-31115 is a high-severity insecure deserialization vulnerability in opensearch-ruby (rubygems), affecting versions >= 2.0.0, < 2.0.2. It is fixed in 2.0.2. Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect.

How severe is CVE-2022-31115?

CVE-2022-31115 has a CVSS score of 8.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of opensearch-ruby are affected by CVE-2022-31115?

opensearch-ruby (rubygems) versions >= 2.0.0, < 2.0.2 is affected.

Is there a fix for CVE-2022-31115?

Yes. CVE-2022-31115 is fixed in 2.0.2. Upgrade to this version or later.

Is CVE-2022-31115 exploitable, and should I be worried?

Whether CVE-2022-31115 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2022-31115 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2022-31115?

Upgrade opensearch-ruby to 2.0.2 or later.

CVE-2022-31115 in opensearch-ruby

Q: How severe is CVE-2022-31115?

CVE-2022-31115 has a CVSS score of 8.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of opensearch-ruby are affected by CVE-2022-31115?

opensearch-ruby (rubygems) versions >= 2.0.0, < 2.0.2 is affected.

Q: Is there a fix for CVE-2022-31115?

Yes. CVE-2022-31115 is fixed in 2.0.2. Upgrade to this version or later.

Q: Is CVE-2022-31115 exploitable, and should I be worried?

Whether CVE-2022-31115 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2022-31115 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2022-31115?

Upgrade opensearch-ruby to 2.0.2 or later.

Summary

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

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:

Open an issue 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.

Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect. Typical impact: arbitrary code execution or logic abuse.

CVE-2022-31115 has a CVSS score of 8.8 (High). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.0.2); upgrading removes the vulnerable code path.

Affected versions

opensearch-ruby (>= 2.0.0, < 2.0.2)

Security releases

opensearch-ruby → 2.0.2 (rubygems)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

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

Frequently Asked Questions

What is CVE-2022-31115? CVE-2022-31115 is a high-severity insecure deserialization vulnerability in opensearch-ruby (rubygems), affecting versions >= 2.0.0, < 2.0.2. It is fixed in 2.0.2. Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect.
How severe is CVE-2022-31115? CVE-2022-31115 has a CVSS score of 8.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of opensearch-ruby are affected by CVE-2022-31115? opensearch-ruby (rubygems) versions >= 2.0.0, < 2.0.2 is affected.
Is there a fix for CVE-2022-31115? Yes. CVE-2022-31115 is fixed in 2.0.2. Upgrade to this version or later.
Is CVE-2022-31115 exploitable, and should I be worried? Whether CVE-2022-31115 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2022-31115 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2022-31115? Upgrade opensearch-ruby to 2.0.2 or later.