CVE-2024-25128: Flask-AppBuilder vulnerable to incorrect authentication when using auth type OpenID
(updated )
When Flask-AppBuilder is set to AUTH_TYPE AUTH_OID, 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 old (deprecated 10 years ago) OpenID 2.0 authorization protocol (which is very different from the popular OIDC - Open ID Connect - popular protocol used today). Currently, this protocol is regarded as legacy, with significantly reduced usage and not supported for several years by major authorization providers.
References
- github.com/advisories/GHSA-j2pw-vp55-fqqj
- github.com/dpgaspar/Flask-AppBuilder/commit/6336456d83f8f111c842b2b53d1e89627f2502c8
- github.com/dpgaspar/Flask-AppBuilder/security/advisories/GHSA-j2pw-vp55-fqqj
- github.com/pypa/advisory-database/tree/main/vulns/flask-appbuilder/PYSEC-2026-340.yaml
- nvd.nist.gov/vuln/detail/CVE-2024-25128
- pypi.org/project/flask-appbuilder
Code Behaviors & Features
Detect and mitigate CVE-2024-25128 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Dependency Scanning using SBOM also detects vulnerabilities from proprietary advisories that this site does not include. Learn more about Dependency Scanning using SBOM →