Skip to content
Fencer Intel
medium 6.8

CVE-2013-0233 json

Devise does not properly perform type conversion when performing database queries

published 2013-04-25 13 y ago modified 2026-06-16 4 mo ago also GHSA-jxhw-mg8m-2pj8 , EUVD-2017-0267

cvss
6.8
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
14.1%
EPSS 14.1% chance of exploitation in 30 days, percentile 96%
public exploits
1
Metasploit

Summary

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.

Patch / fix

  • rubygems devise 1.5.4, 2.0.5, 2.1.3, 2.2.3
  • ruby-devise Debian 12 3.4.1-1

debian advisories DEBIAN-CVE-2013-0233

Timeline

  1. First public exploit (Metasploit auxiliary/admin/http/rails_devise_pass_reset)
  2. Published

Exploit prediction

14.13% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • Metasploit auxiliary/admin/http/rails_devise_pass_reset Ruby on Rails Devise Authentication Password Reset metasploit auxiliary, normal rank, 2013-01-28
  • metasploit.com http://www.metasploit.com/modules/auxiliary/admin/http/rails_devise_pass_reset referenced PoC, tagged "exploit" by a source, unverified
  • phenoelit.org http://www.phenoelit.org/blog/archives/2013/02/05/mysql_madness_and_rails/index.html referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 6.8 AV:N/AC:M/Au:N/C:P/I:P/A:P

Affected packages

ecosystem package affected fixed in
rubygems devise
>=2.2.0, <2.2.3
>=2.1.0, <2.1.3
>=2.0.0, <2.0.5
>=1.5.0, <1.5.4
2.2.3
2.1.3
2.0.5
1.5.4

Classification

Weakness
  • CWE-399 Resource Management Errors
  • CWE-704 Incorrect Type Conversion or Cast

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.