Advisory

GHSA-592j-995h-p23j

Also known as: CVE-2024-27281

Summary

RDoc RCE vulnerability with .rdoc_options

Details

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.

We recommend to update the RDoc gem to version 6.6.3.1 or later. In order to ensure compatibility with bundled version in older Ruby series, you may update as follows instead:

  • For Ruby 3.0 users: Update to rdoc 6.3.4.1
  • For Ruby 3.1 users: Update to rdoc 6.4.1.1
  • For Ruby 3.2 users: Update to rdoc 6.5.1.1

You can use gem update rdoc to update it. If you are using bundler, please add gem "rdoc", ">= 6.6.3.1" to your Gemfile.

Note: 6.3.4, 6.4.1, 6.5.1 and 6.6.3 have a incorrect fix. We recommend to upgrade 6.3.4.1, 6.4.1.1, 6.5.1.1 and 6.6.3.1 instead of them.

Severity

Low Basis: The source's own band: LOW

Dates

Published
2024-03-25 19:36 UTC
Modified
2026-09-10 03:50 UTC

Affected packages and fixes

rdoc

RubyGems · All systems

Affected

  • introduced 6.3.3, fixed 6.3.4.1 (ecosystem)

Fixed versions

6.3.4.1

Fix

The export has no generic command for this ecosystem.

rdoc

RubyGems · All systems

Affected

  • introduced 6.4.0, fixed 6.4.1.1 (ecosystem)

Fixed versions

6.4.1.1

Fix

The export has no generic command for this ecosystem.

rdoc

RubyGems · All systems

Affected

  • introduced 6.5.0, fixed 6.5.1.1 (ecosystem)

Fixed versions

6.5.1.1

Fix

The export has no generic command for this ecosystem.

rdoc

RubyGems · All systems

Affected

  • introduced 6.6.0, fixed 6.6.3.1 (ecosystem)

Fixed versions

6.6.3.1

Fix

The export has no generic command for this ecosystem.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences