Security vulnerabilities

  • Status Closed
  • Assigned To
    cbay
  • Private
Attached to Project: Security vulnerabilities
Opened by nexxp - 23.08.2025
Last edited by cbay - 25.08.2025

FS#204 - Title: Expired TOTP Code Accepted – Broken 2FA Validation

#Description:
During testing, I found that the TOTP code verification does not properly validate the expiry window. Even after waiting for the OTP to expire (30s), I was still able to use the expired code to perform sensitive actions like updating my profile.

#Impact:

Replay attack possible using previously used OTPs.

Weakens 2FA mechanism.

May allow attackers to bypass intended security checks.

#Steps to Reproduce:

Enable 2FA on account.

Generate OTP via authenticator app.

Wait for 30 seconds until OTP expires.

Submit the expired OTP.

Server still processes the action (profile updated).

#Expected Behavior:
The expired OTP should be rejected.

#Actual Behavior:
Expired OTP is accepted.

Closed by  cbay
25.08.2025 09:15
Reason for closing:  Invalid
Admin
cbay commented on 25.08.2025 09:15

Hello,

We do accept OTP that are slightly expired to accommodate for network or human latency, as suggested in https://datatracker.ietf.org/doc/html/rfc6238#section-5.2.

Kind regards,
Cyril

Loading...

Available keyboard shortcuts

Tasklist

Task Details

Task Editing