Alerts This Week
Warning Icon 1 1,154
Alerts This Week
Warning Icon 1 1,154

Gentoo: GLSA-202408-24 Normal: Ruby on Rails Remote Code Execution

gentoo
Calendar Grey August 11, 2024
Dist Gentoo Esm H88
Gentoo GLSA 202408-25 highlights a critical vulnerability in Apache HTTP Server, urging immediate updates to maintain system integrity.
A vulnerability has been discovered in Ruby on Rails, which can lead to remote code execution via serialization of data.

Summary

Multiple vulnerabilities have been discovered in Ruby on Rails. Please review the CVE identifiers referenced below for details.

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

[ 1 ] CVE-2022-32224 https://nvd.nist.gov/vuln/detail/CVE-2022-32224

Availability

This GLSA and any updates to it are available for viewing at the Gentoo Security Website:
https://security.gentoo.org/glsa/202408-24
style>.gentoo_availability{display:block;}

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.

Severity: Normal
Title: Ruby on Rails: Remote Code Execution
Date: August 11, 2024
Bugs: #857840
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.

Get the latest News and Insights

Get the latest Linux and open source security news straight to your inbox.

Affected Packages

Package Vulnerable Unaffected -------------- ------------- -------------- dev-ruby/rails < 6.1.6.1:6.1 >= 6.1.6.1:6.1 < 7.0.3.1:7.0 >= 7.0.3.1:7.0

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.

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.

Your message here