CVE-2024-27281: Medium severity rubygems/rdoc vulnerability

Published Mar 21, 2024
·
Updated

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 .rdocoptions (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.

Other sources

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 .rdocoptions (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.

GitHub

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 .rdocoptions (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.

Launchpad

Affected Software

9 affected componentsFixes available
rubygems/rdoc>=6.3.3<6.3.4.1
6.3.4.1
rubygems/rdoc>=6.6.0<6.6.3.1
6.6.3.1
rubygems/rdoc>=6.5.0<6.5.1.1
6.5.1.1
rubygems/rdoc>=6.4.0<6.4.1.1
6.4.1.1
debian/ruby2.7<=2.7.4-1+deb11u1
2.7.4-1+deb11u5
debian/ruby3.1<=3.1.2-8.5
3.1.2-7+deb12u1
redhat/rdoc<6.3.4.1
6.3.4.1
redhat/rdoc<6.4.1.1
6.4.1.1
redhat/rdoc<6.5.1.1
6.5.1.1

Event History

Mar 21, 2024
Data Sourced
via Red Hat·05:48 PM
DescriptionSeverityAffected Software
Mar 25, 2024
Advisory Published
via GitHub·07:36 PM
May 8, 2024
CVE Published
via MITRE·08:56 PM
Data Sourced
via MITRE·08:56 PM
Description
May 14, 2024
Data Sourced
via NVD·03:11 PM
DescriptionSeverityWeakness
Jun 19, 2024
Data Sourced
via Launchpad·12:12 PM
Description
Feb 14, 2025
Data Sourced
via Ubuntu·09:22 PM
RemedyDescriptionSeverityAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2024-27281?

CVE-2024-27281 has a critical severity rating due to the potential for remote code execution.

2

How do I fix CVE-2024-27281?

To fix CVE-2024-27281, update RDoc to version 6.3.4.1 or later for affected versions.

3

What software is affected by CVE-2024-27281?

CVE-2024-27281 affects RDoc versions 6.3.3 through 6.6.2 distributed in Ruby 3.x through 3.3.0.

4

What could happen if CVE-2024-27281 is exploited?

Exploitation of CVE-2024-27281 could allow attackers to perform remote code execution on affected systems.

5

Is there a workaround for CVE-2024-27281 if I cannot update?

There are no known workarounds for CVE-2024-27281, and updating is the recommended solution.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203