Ruby security fixes need to reach the application that does the work

A fixed release only helps once it reaches the environment doing the work. Businesses need to establish where Ruby is used and who owns the change.

By · CEO of Lyntev

Published . Revised

Event date:

HTML and JavaScript photographed on a screen in 2016
HTML and JavaScript photographed on a screen in 2016. Software maintenance context image; not Ruby code or a demonstration of the vulnerability. · Martin Vorel · CC BY-SA 4.0

The Ruby project recommends upgrading to 3.3.14, 3.4.13 or 4.0.10 following disclosure of vulnerabilities involving regular expressions and strings. In a 20 November article, Cloudflare describes WAF protection for one of the flaws while making clear that it does not replace updating the software.

Establish the inventory first

A business owner may never have chosen Ruby yet still depend on a service built with it. The useful question for a supplier is specific: does this application include an affected version, and what is the correction plan? A substantiated answer identifies the product, the installed version and the environment examined.

In my view, communication about an update must cross the boundary between the technical team and management. Saying that a problem is resolved is insufficient; the record should explain what changed, what was checked and who is watching for side effects.

Check the work after the update

Consider a fictional application that receives requests and sends confirmations. After updating, the team checks a test request, its record and delivery of the confirmation. If work is processed in the background, that path needs checking too. The aim is to verify the service provided, rather than merely an installation-success message.

Prepare recovery before the intervention and decide which signals would justify rolling back. The decision depends on the application; there is no universal command that replaces understanding the system.

Protection has a boundary

A WAF acts on traffic that actually passes through it. I would therefore ask the technical owner to explain the request path and the conditions of protection, without assuming that an announced rule covers every deployment.

This report provides neither an exposure diagnosis nor an exploit test. Its practical conclusion concerns maintenance: identify the dependency, install the appropriate correction and retain a functional check. That chain of responsibility turns a security notice into a completed intervention.

Sources consulted

  1. Ruby — Multiple vulnerabilities in Regexp and StringRuby. Date stated by the source: . Accessed: .
  2. How Cloudflare WAF protects against ruby2shellCloudflare. Date stated by the source: . Accessed: .
  3. Security advisory GHSA-34m4-m9fh-gqp5Ruby / GitHub. Date stated by the source: . Accessed: .

Editorial responsibility

Text and analysis: Wellinton Oliveira, CEO of Lyntev. Sources and the limits of the available information are identified on this page.

Documentary checks of the identified sources, distinguishing announcements, confirmed information and editorial interpretation. No interviews or product tests were carried out for this report.

Wellinton Oliveira

Written by

CEO of Lyntev

Technology with context, original analysis and sources you can consult.