Dpgaspar Flask-appbuilder 4.1.1

CPE Details

Dpgaspar Flask-appbuilder 4.1.1
4.1.1
2025-03-07
13h37 +00:00
2025-03-07
13h37 +00:00
Alerte pour un CPE
Restez informé de toutes modifications pour un CPE spécifique.
Gestion des notifications

CPE Name: cpe:2.3:a:dpgaspar:flask-appbuilder:4.1.1:*:*:*:*:*:*:*

Informations

Vendor

dpgaspar

Product

flask-appbuilder

Version

4.1.1

Related CVE

Open and find in CVE List

CVE ID Publié Description Score Gravité
CVE-2025-58065 2025-09-11 17h55 +00:00 Flask-AppBuilder is an application development framework. Prior to version 4.8.1, when Flask-AppBuilder is configured to use OAuth, LDAP, or other non-database authentication methods, the password reset endpoint remains registered and accessible, despite not being displayed in the user interface. This allows an enabled user to reset their password and be able to create JWT tokens even after the user is disabled on the authentication provider. Users should upgrade to Flask-AppBuilder version 4.8.1 or later to receive a fix. If immediate upgrade is not possible, manually disable password reset routes in the application configuration; implement additional access controls at the web server or proxy level to block access to the reset my password URL; and/or monitor for suspicious password reset attempts from disabled accounts.
6.5
Moyen
CVE-2023-29005 2023-04-10 20h47 +00:00 Flask-AppBuilder versions before 4.3.0 lack rate limiting which can allow an attacker to brute-force user credentials. Version 4.3.0 includes the ability to enable rate limiting using `AUTH_RATE_LIMITED = True`, `RATELIMIT_ENABLED = True`, and setting an `AUTH_RATE_LIMIT`.
7.5
Haute
CVE-2022-31177 2022-08-01 19h05 +00:00 Flask-AppBuilder is an application development framework built on top of Flask python framework. In versions prior to 4.1.3 an authenticated Admin user could query other users by their salted and hashed passwords strings. These filters could be made by using partial hashed password strings. The response would not include the hashed passwords, but an attacker could infer partial password hashes and their respective users. This issue has been fixed in version 4.1.3. Users are advised to upgrade. There are no known workarounds for this issue.
2.7
Bas