RDoc RCE vulnerability with .rdoc_options
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| rdoc RubyGems |
|
|
| Product | Affected | Fixed in |
|---|---|---|
| rdoc RubyGems |
|
|
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.
From the CVE record · mitre
RDoc can restore unrestricted classes when parsing a crafted .rdoc_options YAML file or loading a crafted documentation cache. This can cause object injection and remote code execution. The input does not specify network access, authentication, or user-interaction requirements.
Check installations of the RubyGems rdoc package in the affected ranges: >=6.3.3 <6.3.4.1, >=6.4.0 <6.4.1.1, >=6.5.0 <6.5.1.1, or >=6.6.0 <6.6.3.1.