Active Record component in Ruby on Rails has a data-type injection vulnerability
The Active Record component in Ruby on Rails 2.3.x, 3.0.x, 3.1.x, and 3.2.x does not ensure that the declared data type of a database column is used during comparisons of input values to stored values in that column, which makes it easier for remote attackers to conduct data-type injection attacks against Ruby on Rails applications via a crafted value, as demonstrated by unintended interaction between the "typed XML" feature and a MySQL database.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2013-3221US | medium6.4 | — | ||
The Active Record component in Ruby on Rails 2.3.x, 3.0.x, 3.1.x, and 3.2.x does not ensure that the declared data type of a database column is used during comparisons of input val… | ||||
02
references
External citations — patches, advisories, analysis.
- http://openwall.com/lists/oss-security/2013/02/06/7WEB
- http://openwall.com/lists/oss-security/2013/04/24/7WEB
- http://pl.reddit.com/r/netsec/comments/17yajp/mysql_madness_and_railsWEB
- https://github.com/rails/railsPACKAGE
- https://github.com/rubysec/ruby-advisory-db/blob/master/gems/activerecord/CVE-2013-3221.ymlWEB
- https://groups.google.com/group/rubyonrails-security/msg/1f3bc0b88a60c1ce?dmode=source&output=gplainWEB
- https://nvd.nist.gov/vuln/detail/CVE-2013-3221ADVISORY
- https://web.archive.org/web/20130825191249/http://www.phenoelit.org/blog/archives/2013/02/index.htmlWEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan