CVE-2024-11717

Tokens in CTFd used for account activation and password resetting can be used interchangeably for these operations. When used, they are sent to the server as a GET parameter and they are not single use, which means, that during token expiration time an on-path attacker might reuse such a token to change user's password and take over the account. Moreover, the tokens also include base64 encoded user email. This issue impacts releases up to 3.7.4 and was addressed by pull request 2679 https://github.com/CTFd/CTFd/pull/2679  included in 3.7.5 release.

Tokens in CTFd used for account activation and password resetting can be used interchangeably for these operations. When used, they are sent to the server as a GET parameter and they are not single use, which means, that during token expiration time an on-path attacker might reuse such a token to change user's password and take over the account. Moreover, the tokens also include base64 encoded user email. This issue impacts releases up to 3.7.4 and was addressed by pull request 2679 https://github.com/CTFd/CTFd/pull/2679  included in 3.7.5 release.

Los tokens en CTFd que se usan para activar cuentas y restablecer contraseñas se pueden usar indistintamente para estas operaciones. Cuando se usan, se envían al servidor como un parámetro GET y no son de un solo uso, lo que significa que, durante el tiempo de expiración del token, un atacante en la ruta podría reutilizar dicho token para cambiar la contraseña del usuario y tomar el control de la cuenta. Además, los tokens también incluyen el correo electrónico del usuario codificado en base64. Este problema afecta a las versiones hasta la 3.7.4 y se solucionó mediante la solicitud de incorporación de cambios 2679 https://github.com/CTFd/CTFd/pull/2679 incluida en la versión 3.7.5.