Ruby fixes seven memory-safety flaws, with remote code execution proof-of-concepts for some
Ruby released 4.0.10, 3.4.13 and 3.3.14 to fix seven memory-safety flaws in its regular expression engine and string case-conversion code; some flaws have remote code execution proof-of-concepts.
According to The Hacker News, Ruby released versions 4.0.10, 3.4.13 and 3.3.14 to fix seven memory-safety flaws in its regular expression engine and string case-conversion code. The seven flaws had no CVE (Common Vulnerabilities and Exposures) numbers assigned at publication and are tracked by GitHub Security Advisory (GHSA) IDs. The maintainers said they are aware of proof-of-concepts (PoCs) proving some of the flaws can trigger remote code execution, while the report says the advisories record no attacks so far.
What is affected
The affected range is Ruby 4.0.0 through 4.0.9, fixed in 4.0.10. The affected range is Ruby 3.4.0 through 3.4.12, fixed in 3.4.13. The report lists Ruby 3.3.13 and earlier as the affected range, fixed in 3.3.14, and Ruby 3.2 and earlier as end of life with no fixes.
Why it matters
The advisories rate three flaws critical, three high and one moderate. Because the fixes ship inside Ruby, updating an application’s gems or framework does not replace a vulnerable interpreter.
What to do
Update the Ruby runtime on servers, workers and container images to the fixed release for each listed range: 4.0.10 for 4.0.0 through 4.0.9, 3.4.13 for 3.4.0 through 3.4.12, and 3.3.14 for the range given as 3.3.13 and earlier. Ruby 3.2 and earlier are end of life and will not receive fixes.
Sources
Related reading
3 postsDiscussion
Spotted an error? Send corrections to [email protected] .