Devise does not properly perform type conversion when performing database queries
Devise gem 2.2.x before 2.2.3, 2.1.x before 2.1.3, 2.0.x before 2.0.5, and 1.5.x before 1.5.4 for Ruby, when using certain databases, does not properly perform type conversion when performing database queries, which might allow remote attackers to cause incorrect results to be returned and bypass security checks via unknown vectors, as demonstrated by resetting passwords of arbitrary accounts.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2013-0233US | medium6.8 | Exploit | ||
Devise gem 2.2.x before 2.2.3, 2.1.x before 2.1.3, 2.0.x before 2.0.5, and 1.5.x before 1.5.4 for Ruby, when using certain databases, does not properly perform type conversion when… | ||||
02
references
External citations — patches, advisories, analysis.
- http://blog.plataformatec.com.br/2013/01/security-announcement-devise-v2-2-3-v2-1-3-v2-0-5-and-v1-5-3-releasedWEB
- http://lists.opensuse.org/opensuse-updates/2013-03/msg00000.htmlWEB
- http://www.metasploit.com/modules/auxiliary/admin/http/rails_devise_pass_resetWEB
- http://www.openwall.com/lists/oss-security/2013/01/29/3WEB
- https://github.com/Snorby/snorby/issues/261WEB
- https://nvd.nist.gov/vuln/detail/CVE-2013-0233ADVISORY
- https://web.archive.org/web/20140726005251/http://www.phenoelit.org/blog/archives/2013/02/05/mysql_madness_and_rails/index.htmlWEB
- https://web.archive.org/web/20200229103406/http://www.securityfocus.com/bid/57577WEB
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