The cross-site scripting (XSS) prevention feature in Ruby on Rails 2.x before 2.3.12, 3.0.x before 3.0.8, and 3.1.x before 3.1.0.rc2 does not properly handle mutation of safe buffers, which makes it easier for remote attackers to conduct XSS attacks via crafted strings to an application that uses a problematic string method, as demonstrated by the sub method.
CVE-2011-2197 is a security vulnerability that . Impacting 2 products from rubyonrails, from rubyonrails organizations running these solutions should prioritize assessment and patching.
Documented in 2011, this vulnerability occurred amid the cloud computing expansion era, where traditional network perimeter security models were being reevaluated. Organizations were transitioning from isolated infrastructure to interconnected systems, creating new attack surfaces that vulnerabilities like this could exploit.
2011-06-30T15:55:01.910
2025-04-11T00:51:21.963
Deferred
CVSSv2: 4.3 (MEDIUM)
AV:N/AC:M/Au:N/C:N/I:P/A:N
8.6
2.9
| Type | Vendor | Product | Version/Range | Vulnerable? |
|---|---|---|---|---|
| Application | rubyonrails | rails | 2.0.0 | Yes |
| Application | rubyonrails | rails | 2.0.0 | Yes |
| Application | rubyonrails | rails | 2.0.0 | Yes |
| Application | rubyonrails | rails | 2.0.1 | Yes |
| Application | rubyonrails | rails | 2.0.2 | Yes |
| Application | rubyonrails | rails | 2.0.4 | Yes |
| Application | rubyonrails | rails | 2.1.0 | Yes |
| Application | rubyonrails | rails | 2.1.1 | Yes |
| Application | rubyonrails | rails | 2.1.2 | Yes |
| Application | rubyonrails | rails | 2.2.0 | Yes |
| Application | rubyonrails | rails | 2.2.1 | Yes |
| Application | rubyonrails | rails | 2.2.2 | Yes |
| Application | rubyonrails | rails | 2.3.2 | Yes |
| Application | rubyonrails | rails | 2.3.3 | Yes |
| Application | rubyonrails | rails | 2.3.4 | Yes |
| Application | rubyonrails | rails | 2.3.9 | Yes |
| Application | rubyonrails | rails | 2.3.10 | Yes |
| Application | rubyonrails | rails | 2.3.11 | Yes |
| Application | rubyonrails | rails | 3.0.0 | Yes |
| Application | rubyonrails | rails | 3.0.0 | Yes |
| Application | rubyonrails | rails | 3.0.0 | Yes |
| Application | rubyonrails | rails | 3.0.0 | Yes |
| Application | rubyonrails | rails | 3.0.0 | Yes |
| Application | rubyonrails | rails | 3.0.0 | Yes |
| Application | rubyonrails | rails | 3.0.0 | Yes |
| Application | rubyonrails | rails | 3.0.1 | Yes |
| Application | rubyonrails | rails | 3.0.1 | Yes |
| Application | rubyonrails | rails | 3.0.2 | Yes |
| Application | rubyonrails | rails | 3.0.2 | Yes |
| Application | rubyonrails | rails | 3.0.3 | Yes |
| Application | rubyonrails | rails | 3.0.4 | Yes |
| Application | rubyonrails | rails | 3.0.5 | Yes |
| Application | rubyonrails | rails | 3.0.5 | Yes |
| Application | rubyonrails | rails | 3.0.6 | Yes |
| Application | rubyonrails | rails | 3.0.6 | Yes |
| Application | rubyonrails | rails | 3.0.6 | Yes |
| Application | rubyonrails | rails | 3.0.7 | Yes |
| Application | rubyonrails | rails | 3.0.7 | Yes |
| Application | rubyonrails | rails | 3.0.7 | Yes |
| Application | rubyonrails | rails | 3.0.8 | Yes |
| Application | rubyonrails | rails | 3.0.8 | Yes |
| Application | rubyonrails | rails | 3.0.8 | Yes |
| Application | rubyonrails | rails | 3.0.8 | Yes |
| Application | rubyonrails | ruby_on_rails | 3.0.4 | Yes |
| Application | rubyonrails | rails | 3.1.0 | Yes |
| Application | rubyonrails | rails | 3.1.0 | Yes |
| Application | rubyonrails | rails | 3.1.0 | Yes |
SecUtils normalizes and enriches National Vulnerability Database (NVD) records by standardizing vendor and product identifiers, aggregating vulnerability metadata from both NVD and MITRE sources, and providing structured context for security teams. For rubyonrails's affected products, we extract Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) classifications, CVSS severity metrics, and reference data to enable rapid vulnerability prioritization and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and security operations.