An advisory reports an unauthenticated remote code execution vulnerability affecting Ruby versions back to 2.4.0. Patches are available for Ruby 3.3 and later. How should we approach this, especially for older installations?
What should we do about the unauthenticated Ruby RCE advisory?
Answers
First, inventory the Ruby versions running in production, including packaged applications and container images. For installations on supported Ruby branches, check the advisory for the fixed version and update to that release or newer.
Then rebuild and redeploy any affected images. Updating Ruby on a host won't fix a separate copy baked into a container.
Reply to this answer
For anything older than 3.3, don't assume there's a patch available just because newer branches have one. Check whether your application or operating system vendor has issued a fix, and plan an upgrade to a supported Ruby version if not.
Before treating every installation as equally exposed, read the advisory's conditions and check whether the affected functionality is reachable in your setup. If you can't determine that quickly, restrict access where practical while you investigate.
Reply to this answer
The version range alone doesn't tell you exactly which services can be exploited. Check the advisory for the affected component, prerequisites, and any mitigation guidance before deciding what to take offline.
Prioritize systems that accept untrusted network traffic, then verify the running version after deployment. Keep an eye on the advisory for updates, since the CVE was still pending in the initial report.
Reply to this answer
Add your answer
Answers are reviewed before publication.
5j+claspfunnel_847:
Worth checking vendor advisories too. A distribution may identify a fix by its own package version rather than the upstream Ruby version.