GLSA 202408-24: Ruby on Rails: Remote Code Execution
| Severity: | normal |
| Title: | Ruby on Rails: Remote Code Execution |
| Date: | 08/11/2024 |
| Bugs: | |
| ID: | 202408-24 |
Synopsis
A vulnerability has been discovered in Ruby on Rails, which can lead to remote code execution via serialization of data.Background
Ruby on Rails is a free web framework used to develop database-driven web applications.
Affected packages
| Package | Vulnerable | Unaffected | Architecture(s) |
|---|---|---|---|
| dev-ruby/rails | < 7.0.3.1 | >= 7.0.3.1 | All supported architectures |
Description
Multiple vulnerabilities have been discovered in Ruby on Rails. Please review the CVE identifiers referenced below for details.
Impact
When serialized columns that use YAML (the default) are deserialized, Rails uses YAML.unsafe_load to convert the YAML data in to Ruby objects. If an attacker can manipulate data in the database (via means like SQL injection), then it may be possible for the attacker to escalate to an RCE. Impacted Active Record models will look something like this: class User < ApplicationRecord serialize :options # Vulnerable: Uses YAML for serialization serialize :values, Array # Vulnerable: Uses YAML for serialization serialize :values, JSON # Not vulnerable end The released versions change the default YAML deserializer to use YAML.safe_load, which prevents deserialization of possibly dangerous objects. This may introduce backwards compatibility issues with existing data.
Workaround
There is no known workaround at this time.
Resolution
All Ruby on Rails users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose ">=dev-ruby/rails-6.1.6.1:6.1"
# emerge --ask --oneshot --verbose ">=dev-ruby/rails-7.0.3.1:7.0"
References
Availability
This GLSA and any updates to it are available for viewing at the Gentoo Security Website:
Concerns?
Security is a primary focus of Gentoo Linux and ensuring the confidentiality and security of our users machines is of utmost importance to us. Any security concerns should be addressed to security@gentoo.org or alternatively, you may file a bug at https://bugs.gentoo.org.
License
Copyright 2010 Gentoo Foundation, Inc; referenced text belongs to its owner(s). The contents of this document are licensed under the Creative Commons - Attribution / Share Alike license.
