Skip to content

TOTP can be brute forced

Moderate
ChrisMacNaughton published GHSA-qrqh-v2j6-3g7w Jan 11, 2024

Package

bundler EyeDP (RubyGems)

Affected versions

<= 1.0.16, < 1.1

Patched versions

1.0.17, 1.1.0-rc4

Description

Impact

If a user's username and password is known to an attacker, it is possible to brute force their TOTP.

The following log line will be triggered and can be used to detect this kind of attack:

Rails.logger.warn("Failed Login: user=#{user.username} ip=#{request.remote_ip} method=OTP")

Patches

A fix is in progress

Workarounds

It is possible to limit the availability of this attack by configuring a rate-limit on the login endpoints via Nginx or similar

References

GHSA-chcr-x7hc-8fp8

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
Low
Integrity
Low
Availability
Low

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:L/I:L/A:L

CVE ID

CVE-2024-0227

Weaknesses