https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-05T16:54:29.845705+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/cnvd-2015-07334 cnvd-2015-07334 2026-10-05T16:54:29.926766+00:00 cnvd-2015-07334 https://cve.radiocsirt.org/vuln/euvd-2026-94806 EUVD-2026-94806 2026-10-05T16:54:29.926806+00:00 EUVD-2026-94806 https://cve.radiocsirt.org/vuln/fkie_cve-2015-7225 fkie_cve-2015-7225 2026-10-05T16:54:29.926820+00:00

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.

 https://cve.radiocsirt.org/vuln/ghsa-x489-jjwm-52g7 GHSA-x489-jjwm-52g7 — Tinfoil Devise-two-factor does not "burn" a successfully validated one-time password (OTP) 2026-10-05T16:54:29.926852+00:00

Affected: RubyGems: devise-two-factor

Tinfoil Devise-two-factor before 2.0.0 does not strictly follow [RFC 6238 § 5.2 ](https://datatracker.ietf.org/doc/html/rfc6238#section-5.2) and does not "burn" a successfully validated one-time password (aka OTP), which allows 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.

 https://cve.radiocsirt.org/vuln/gsd-2015-7225 gsd-2015-7225 2026-10-05T16:54:29.926881+00:00 gsd-2015-7225 https://cve.radiocsirt.org/vuln/ubuntu-cve-2015-7225 Withdrawn: UBUNTU-CVE-2015-7225 2026-10-05T16:54:29.926892+00:00

Withdrawn by the publisher.

Affected: Ubuntu:16.04:LTS: ruby-devise-two-factor

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.