Arbitrary Code Injection Affecting ruby:2.5/rubygem-mysql2-doc package, versions <0:0.4.10-4.module+el8.9.0+19193+435404ae


Severity

Recommended
0.0
medium
0
10

Based on Red Hat Enterprise Linux security rating.

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Arbitrary Code Injection vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-RHEL8-RUBY-6683525
  • published27 Apr 2024
  • disclosed21 Mar 2024

Introduced: 21 Mar 2024

CVE-2024-27281  (opens in a new tab)
CWE-94  (opens in a new tab)

How to fix?

Upgrade RHEL:8 ruby:2.5/rubygem-mysql2-doc to version 0:0.4.10-4.module+el8.9.0+19193+435404ae or higher.
This issue was patched in RHSA-2024:4499.

NVD Description

Note: Versions mentioned in the description apply only to the upstream ruby:2.5/rubygem-mysql2-doc package and not the ruby:2.5/rubygem-mysql2-doc package as distributed by RHEL. See How to fix? for RHEL:8 relevant fixed versions and status.

An issue was discovered in RDoc 6.3.3 through 6.6.2, as distributed in Ruby 3.x through 3.3.0. When parsing .rdoc_options (used for configuration in RDoc) as a YAML file, object injection and resultant remote code execution are possible because there are no restrictions on the classes that can be restored. (When loading the documentation cache, object injection and resultant remote code execution are also possible if there were a crafted cache.) The main fixed version is 6.6.3.1. For Ruby 3.0 users, a fixed version is rdoc 6.3.4.1. For Ruby 3.1 users, a fixed version is rdoc 6.4.1.1. For Ruby 3.2 users, a fixed version is rdoc 6.5.1.1.

CVSS Scores

version 3.1