CVE-2024-5213

In mintplex-labs/anything-llm versions up to and including 1.5.3, an issue was discovered where the password hash of a user is returned in the response after login (`POST /api/request-token`) and after account creations (`POST /api/admin/users/new`). This exposure occurs because the entire User object, including the bcrypt password hash, is included in the response sent to the frontend. This practice could potentially lead to sensitive information exposure despite the use of bcrypt, a strong hashing algorithm. It is recommended not to expose any clues about passwords to the frontend.

In mintplex-labs/anything-llm versions up to and including 1.5.3, an issue was discovered where the password hash of a user is returned in the response after login (`POST /api/request-token`) and after account creations (`POST /api/admin/users/new`). This exposure occurs because the entire User object, including the bcrypt password hash, is included in the response sent to the frontend. This practice could potentially lead to sensitive information exposure despite the use of bcrypt, a strong hashing algorithm. It is recommended not to expose any clues about passwords to the frontend.

En las versiones de mintplex-labs/anything-llm hasta la 1.5.3 incluida, se descubrió un problema por el cual el hash de la contraseña de un usuario se devuelve en la respuesta después de iniciar sesión (`POST /api/request-token`) y después de la creación de la cuenta. (`POST /api/admin/usuarios/nuevo`). Esta exposición se produce porque todo el objeto Usuario, incluido el hash de la contraseña de bcrypt, se incluye en la respuesta enviada al frontend. Esta práctica podría conducir potencialmente a la exposición de información confidencial a pesar del uso de bcrypt, un potente algoritmo hash. Se recomienda no exponer ninguna pista sobre contraseñas en la interfaz.