Approved changes feed: RSS · Atom

cpe:2.3:a:tinfoilsecurity:devise-two-factor:*:*:*:*:*:*:*:*

part: a version: * update: *

VendorTinfoilsecurity (54ce5a7c-71fa-552f-a4f5-ddef0257cbab)
ProductDevise Two Factor (73c31f52-3021-5410-b91f-3a1ba3325bb3)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*

Notes

Imported from purl2cpe mapping

PURL mappings

PURLSourceLast updated
pkg:deb/debian/ruby-devise-two-factor purl2cpe 2026-06-01 10:14:07.061690
pkg:deb/ubuntu/ruby-devise-two-factor purl2cpe 2026-06-01 10:14:07.061692
pkg:gem/devise-two-factor purl2cpe 2026-06-01 10:14:07.061694
pkg:github/tinfoil/devise-two-factor purl2cpe 2026-06-01 10:14:07.061696
pkg:rpm/opensuse/rubygem-devise-two-factor purl2cpe 2026-06-01 10:14:07.061698

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2024-8796 vulnerable 2026-06-08 07:00:25.744145 Insufficient Default OTP Shared Secret Length
MEDIUM (5.3)
Under the default configuration, Devise-Two-Factor versions >= 2.2.0 & < 6.0.0 generate TOTP shared secrets that are 120 bits instead of the 128-bit minimum defined by RFC 4226. Using a shared secret shorter than the minimum to generate a multi-factor authentication code could make it easier for an attacker to guess the shared secret and generate valid TOTP codes.
Published: 2024-09-17T17:12:13.468Z
Updated: 2024-09-20T19:43:21.263Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2021-43177 vulnerable 2026-06-08 05:36:42.380688 Details available
As a result of an incomplete fix for CVE-2015-7225, in versions of devise-two-factor prior to 4.0.2 it is possible to reuse a One-Time-Password (OTP) for one (and only one) immediately trailing interval. CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N)
Published: 2022-04-11T19:37:40.000Z
Updated: 2024-08-04T03:47:13.623Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2015-7225 vulnerable 2026-06-08 05:07:00.150063 Details available
Tinfoil Devise-two-factor before 2.0.0 does not strictly follow section 5.2 of RFC 6238 and does not "burn" a successfully validated one-time password (aka OTP), which allows remote or physically proximate attackers with a target user's login credentials to log in as said user by obtaining the OTP through performing a man-in-the-middle attack between the provider and verifier, or shoulder surfing, and replaying the OTP in the current time-step.
Published: 2017-09-06T21:00:00.000Z
Updated: 2024-08-06T07:43:45.764Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.

Inspect record JSON

Open JSON directly

Open this panel to browse, search, copy or download the JSON record.