Skip to content

Update ruby ReDoS guidance to reflect improved handling in 3.2.0

Nick Malcolm requested to merge secure-code-ruby-redos into master

What does this MR do and why?

Newer ruby versions aren't (as) vulnerable to ReDoS, and the current example in the secure code guidelines in particular no longer exhibited the denial of service behaviour.

This MR updates our guidance to reflect the current state of things as GitLab continues to transition over to ruby > 3.2.0 + global timeout.

Closes ReDos documentation example runs in linear time (#453995 - closed).

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before After

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

Merge request reports