Skip to content

Improper one time password handling in devise-two-factor

Moderate severity GitHub Reviewed Published Apr 7, 2022 in devise-two-factor/devise-two-factor • Updated May 4, 2023

Package

bundler devise-two-factor (RubyGems)

Affected versions

< 4.0.2

Patched versions

4.0.2

Description

Impact

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.

Patches

This vulnerability has been patched in version 4.0.2 which was released on March 24th, 2022. Individuals using this package are strongly encouraged to upgrade as soon as possible.

Credit for discovery

Benoit Côté-Jodoin
Michael Nipper - devise-two-factor/devise-two-factor#106

References

@bsedat bsedat published to devise-two-factor/devise-two-factor Apr 7, 2022
Published to the GitHub Advisory Database Apr 7, 2022
Reviewed Apr 7, 2022
Published by the National Vulnerability Database Apr 11, 2022
Last updated May 4, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(30th percentile)

Weaknesses

No CWEs

CVE ID

CVE-2021-43177

GHSA ID

GHSA-jm35-h8q2-73mp

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.