dpgaspar Flask-AppBuilder up to 4.3.10 OpenID Service improper authentication
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.0 | $0-$5k | 0.00 |
Summary
A vulnerability was found in dpgaspar Flask-AppBuilder up to 4.3.10. It has been rated as critical. The affected element is an unknown function of the component OpenID Service Handler. Performing a manipulation results in improper authentication. This vulnerability is cataloged as CVE-2024-25128. It is possible to initiate the attack remotely. There is no exploit available. Upgrading the affected component is advised.
Details
A vulnerability was found in dpgaspar Flask-AppBuilder up to 4.3.10. It has been classified as critical. This affects an unknown function of the component OpenID Service Handler. The manipulation with an unknown input leads to a improper authentication vulnerability. CWE is classifying the issue as CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Flask-AppBuilder is an application development framework, built on top of Flask. When Flask-AppBuilder is set to AUTH_TYPE AUTH_OID, it allows an attacker to forge an HTTP request, that could deceive the backend into using any requested OpenID service. This vulnerability could grant an attacker unauthorised privilege access if a custom OpenID service is deployed by the attacker and accessible by the backend. This vulnerability is only exploitable when the application is using the OpenID 2.0 authorization protocol. Upgrade to Flask-AppBuilder 4.3.11 to fix the vulnerability.
The weakness was shared 02/28/2024. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2024-25128 since 02/05/2024. Neither technical details nor an exploit are publicly available.
Upgrading to version 4.3.11 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.2VulDB Meta Temp Score: 8.0
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 9.1
CNA Vector (GitHub, Inc.): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Improper authenticationCWE: CWE-287
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Flask-AppBuilder 4.3.11
Patch: github.com
Timeline
02/05/2024 🔍02/28/2024 🔍
02/28/2024 🔍
10/15/2025 🔍
Sources
Product: github.comAdvisory: 6336456d83f8f111c842b2b53d1e89627f2502c8
Status: Confirmed
CVE: CVE-2024-25128 (🔍)
GCVE (CVE): GCVE-0-2024-25128
GCVE (VulDB): GCVE-100-255129
Entry
Created: 02/28/2024 16:41Updated: 10/15/2025 02:49
Changes: 02/28/2024 16:41 (49), 04/03/2024 07:01 (16), 04/03/2024 07:15 (1), 10/15/2025 02:49 (2)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.