The email verification mechanism sets a 24-hour expiration window ("Expira en: 23h 59m") for the generated verification code instead of adhering to the recommended security standard of 30 minutes, creating a potential security vulnerability.
Issue Description
When a user triggers an email verification code on the "Verifica tu cuenta" screen, the system assigns a TTL (Time To Live) of 24 hours to the code (displayed as Expira en: 23h 59m).
An extended validity period for One-Time Passwords (OTP) or short-lived verification codes significantly increases the exposure window for brute-force attempts, unauthorized access if an email account is compromised, or replay attacks. The industry-recommended threshold for email OTP codes is 15 to 30 minutes.
Preconditions
User is on the Verifica tu cuenta step of the registration or verification flow.
An email verification code request has been triggered.
Steps to Reproduce
Navigate to the account verification process (Verifica tu cuenta).
Select the Verificación de correo electrónico option.
Trigger the sending of the verification code to the registered email address.
Check the expiration timer label under the Verificación de correo electrónico card.
Observe the remaining validity time displayed by the system.
Expected Result
The email verification code should have a short validity period (recommended: 30 minutes max, e.g., "Expira en: 30m") to maintain secure authentication standards.
Actual Result
The system sets an excessively long expiration time of 24 hours, displaying:
"Expira en: 23h 59m"
Evidence
Email Verification Card: Shows active status with an extended countdown starting at ~24 hours (Expira en: 23h 59m).
UI Context: "Verifica tu cuenta" flow -> "Verificación de correo electrónico" block.
Impact
Security Risk: High risk of unauthorized code utilization within a broad 24-hour attack window.
Compliance & Best Practices Violation: Non-compliance with standard security guidelines (OWASP / NIST) for OTP expiration management.
Frequency
Always
Reproducibility
100%
Notes
Adjust the expiration configuration parameter (TTL) on the backend authentication server/token generator service from 24h (86400 seconds) to 30m (1800 seconds).
Ensure the frontend countdown timer dynamically reflects the updated backend token expiration time.
## Summary
The email verification mechanism sets a 24-hour expiration window ("Expira en: 23h 59m") for the generated verification code instead of adhering to the recommended security standard of 30 minutes, creating a potential security vulnerability.
## Issue Description
When a user triggers an email verification code on the "Verifica tu cuenta" screen, the system assigns a TTL (Time To Live) of 24 hours to the code (displayed as Expira en: 23h 59m).
An extended validity period for One-Time Passwords (OTP) or short-lived verification codes significantly increases the exposure window for brute-force attempts, unauthorized access if an email account is compromised, or replay attacks. The industry-recommended threshold for email OTP codes is 15 to 30 minutes.
## Preconditions
- User is on the *Verifica tu cuenta* step of the registration or verification flow.
- An email verification code request has been triggered.
## Steps to Reproduce
1. Navigate to the account verification process (*Verifica tu cuenta*).
2. Select the *Verificación de correo electrónico* option.
3. Trigger the sending of the verification code to the registered email address.
4. Check the expiration timer label under the *Verificación de correo electrónico* card.
5. Observe the remaining validity time displayed by the system.
## Expected Result
The email verification code should have a short validity period (recommended: 30 minutes max, e.g., "Expira en: 30m") to maintain secure authentication standards.
## Actual Result
The system sets an excessively long expiration time of 24 hours, displaying:
> "Expira en: 23h 59m"
## Evidence
- *Email Verification Card:* Shows active status with an extended countdown starting at ~24 hours (Expira en: 23h 59m).
- *Target Account:* maurodriguez0023@gmail.com
- *UI Context:* "Verifica tu cuenta" flow -> "Verificación de correo electrónico" block.
## Impact
- *Security Risk:* High risk of unauthorized code utilization within a broad 24-hour attack window.
- *Compliance & Best Practices Violation:* Non-compliance with standard security guidelines (OWASP / NIST) for OTP expiration management.
## Frequency
Always
## Reproducibility
100%
## Notes
- Adjust the expiration configuration parameter (TTL) on the backend authentication server/token generator service from 24h (86400 seconds) to 30m (1800 seconds).
- Ensure the frontend countdown timer dynamically reflects the updated backend token expiration time.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
The email verification mechanism sets a 24-hour expiration window ("Expira en: 23h 59m") for the generated verification code instead of adhering to the recommended security standard of 30 minutes, creating a potential security vulnerability.
Issue Description
When a user triggers an email verification code on the "Verifica tu cuenta" screen, the system assigns a TTL (Time To Live) of 24 hours to the code (displayed as Expira en: 23h 59m).
An extended validity period for One-Time Passwords (OTP) or short-lived verification codes significantly increases the exposure window for brute-force attempts, unauthorized access if an email account is compromised, or replay attacks. The industry-recommended threshold for email OTP codes is 15 to 30 minutes.
Preconditions
Steps to Reproduce
Expected Result
The email verification code should have a short validity period (recommended: 30 minutes max, e.g., "Expira en: 30m") to maintain secure authentication standards.
Actual Result
The system sets an excessively long expiration time of 24 hours, displaying:
Evidence
Impact
Frequency
Always
Reproducibility
100%
Notes