CVE-2015-8314: Devise gem · Cleartext Storage of Sensitive Information
Source CVE Database V5
Not known to be exploited · CVSS 7.5 High : upgrade to 3.5.4 soon.
Data as of 26 Oct 2026, 13:47 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 49% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.5.4
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 12 Dec 2023
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade devise to 3.5.4.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
RubyGemsdevisepkg:gem/deviseOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
European organizations should immediately verify the version of the Devise gem used in their Ruby on Rails applications and upgrade to version 3.5.4 or later, where this vulnerability is fixed. Beyond upgrading, organizations should implement additional security controls such as: 1) Enforce secure cookie attributes (Secure, HttpOnly, SameSite) to reduce the risk of cookie theft via network interception or cross-site scripting. 2) Implement short expiration times for Remember Me cookies to limit the window of opportunity for attackers. 3) Use encrypted and signed cookies to prevent tampering and unauthorized use. 4) Monitor authentication logs for unusual session activity that may indicate exploitation attempts. 5) Employ multi-factor authentication (MFA) to reduce reliance on persistent cookies for session management. 6) Conduct regular security assessments and code reviews focusing on session management and authentication mechanisms. 7) Educate developers on secure handling of authentication tokens and session cookies. These measures, combined with patching, will significantly reduce the risk posed by this vulnerability.
Description
The Devise gem before 3.5.4 for Ruby mishandles Remember Me cookies for sessions, which may allow an adversary to obtain unauthorized persistent application access.