CVE-2012-6497: SQL Injection
The Authlogic gem for Ruby on Rails, when used with certain versions before 3.2.10, makes potentially unsafe findbyid method calls, which might allow remote attackers to conduct CVE-2012-6496 SQL injection attacks via a crafted parameter in environments that have a known secrettoken value, as demonstrated by a value contained in secrettoken.rb in an open-source product.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/railsto a version that resolves this vulnerability.Fixed in 2.3.14.1 - Upgrade
Upgrade
debian/railsto a version that resolves this vulnerability.Fixed in 2:6.1.7.10+dfsg-1~deb12u2Fixed in 2:6.1.7.10+dfsg-1~deb12u3Fixed in 2:7.2.2.2+dfsg-2~deb13u1Fixed in 2:7.2.2.2+dfsg-2~deb13u2Fixed in 2:7.2.4+dfsg-2 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 3.2.10
Event History
Frequently Asked Questions
What is the severity of CVE-2012-6497?
CVE-2012-6497 is considered a high severity vulnerability due to its potential for SQL injection attacks.
How do I fix CVE-2012-6497?
To fix CVE-2012-6497, upgrade the Authlogic gem or Rails framework to version 3.2.10 or later.
What versions of Ruby on Rails are affected by CVE-2012-6497?
CVE-2012-6497 affects Ruby on Rails versions prior to 3.2.10.
What kind of attacks can be carried out due to CVE-2012-6497?
CVE-2012-6497 can allow remote attackers to conduct SQL injection attacks via crafted parameters.
Is the find_by_id method in Ruby on Rails safe to use with CVE-2012-6497?
The find_by_id method is potentially unsafe in environments with certain configurations and affected versions related to CVE-2012-6497.