CVE-2013-0233: 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…
Noroxi assessment
Priority: Plan (action score 40/100)
- A ready-made attack module is public (Metasploit); exploiting it takes no special expertise.
- Because a ready-made attack tool exists, priority is at least “Plan”.
- Probability of exploitation in the next 30 days: 14.6% (FIRST EPSS); higher than 96.7% of all records.
- Fixed version: ruby-devise (Debian:12) 3.4.1-1; devise (RubyGems) 1.5.4, 2.0.5, 2.1.3.
Add it to your regular patch cycle. Upgrade to ruby-devise (Debian:12) 3.4.1-1; devise (RubyGems) 1.5.4, 2.0.5, 2.1.3 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Apr 25, 2013
- Updated
- Jun 16, 2026
- EPSS
- 14.6% · 96th percentile
- CWE
- CWE-399
Report tools
Action score
40
Add it to your regular patch cycle.
- CVSS
- 27 / 40 · 6.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 4 / 30 · 14.6%
- Ready-made attack tool
- 9 / 40 · floor: at least 40
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Weaponized exploit exists
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| plataformatec | devise | cpe:2.3:a:plataformatec:devise |
| ruby-lang | ruby | cpe:2.3:a:ruby-lang:ruby |
| opensuse | opensuse | cpe:2.3:o:opensuse:opensuse |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- opensuse opensuse12.2
- plataformatec devise1.5.0
- plataformatec devise1.5.1
- plataformatec devise1.5.2
- plataformatec devise1.5.3
- plataformatec devise2.0.0
- plataformatec devise2.0.1
- plataformatec devise2.0.2
+8 more rows
- plataformatec devise2.0.3
- plataformatec devise2.0.4
- plataformatec devise2.1.0
- plataformatec devise2.1.1
- plataformatec devise2.1.2
- plataformatec devise2.2.0
- plataformatec devise2.2.1
- plataformatec devise2.2.2
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | ruby-devise | before 3.4.1-1 | 3.4.1-1 |
| RubyGems | devise | from 1.5.0 · before 1.5.4 | 1.5.4 |
| RubyGems | devise | from 2.0.0 · before 2.0.5 | 2.0.5 |
| RubyGems | devise | from 2.1.0 · before 2.1.3 | 2.1.3 |
| RubyGems | devise | from 2.2.0 · before 2.2.3 | 2.2.3 |
Same product
plataformatec: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-5421Plataformatec Devise version 4.5.0 and earlier, using the lockable module contains a CWE-367 vulnerability in The…39Monitor
- CVE-2019-16109An issue was discovered in Plataformatec Devise before 4.7.1.22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:ruby-devise | 3.4.1-1 · Debian:12 | Package registry (OSV) |
| RubyGems:devise | 1.5.4 | Package registry (OSV) |
| RubyGems:devise | 2.0.5 | Package registry (OSV) |
| RubyGems:devise | 2.1.3 | Package registry (OSV) |
| RubyGems:devise | 2.2.3 | Package registry (OSV) |
Exploit status
Weaponized
A ready exploit tool or active in-the-wild use is known for this vulnerability. This should be your top priority.
Evidence
- Metasploit module ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Metasploit module | auxiliary/admin/http/rails_devise_pass_resetRuby on Rails Devise Authentication Password Resetauxiliary | 2013-01-28 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Metasploit-88 d
- Published
- TodayNov 16, 2026+4952 d
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate.
Technical details
Attack conditions
If successful
- Confidentiality
- P · data can be read
- Integrity
- P · data or configuration can be modified
- Availability
- P · the service can be disrupted
- Attack complexity
- M
- Confidentiality impact
- P
- Integrity impact
- P
- Availability impact
- P
Weakness class (CWE)
CWE-399 · Resource Management ErrorsCVSS vector
AV:N/AC:M/Au:N/C:P/I:P/A:P
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.