CVE-2024-45314
Dpgaspar Flask-Appbuilder ≤ 4.5.1
Raw vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:L/I:N/A:NSummary
CVE-2024-45314 is a low-severity Use of Web Browser Cache Containing Sensitive Information (CWE-525) vulnerability in Dpgaspar Flask-Appbuilder. Its CVSS base score is 3.6 (Low).
Operationally, exploitation aligns with the MITRE ATT&CK technique Data from Local System (T1005); ranked at the 18th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-2784
Vulnerability Data
Flask-AppBuilder is an application development framework. Prior to version 4.5.1, the auth DB login form default cache directives allows browser to locally store sensitive data. This can be an issue on environments using shared computer resources. Version 4.5.1 contains a…
more
patch for this issue. If upgrading is not possible, configure one's web server to send the specific HTTP headers for `/login` per the directions provided in the GitHub Security Advisory.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V14.2.5V14.3.2
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Endpoint device configuration can enforce cache-clearing or no-cache policies for sensitive web content.
Application security requirements can explicitly require no-cache headers or cache-control directives for sensitive pages.
Secure coding standards can mandate proper cache-control headers and form-field handling to prevent sensitive data retention.
Configuration management can mandate secure browser cache settings across the estate.
Web filtering can block risky sites but does not directly govern browser caching of sensitive data.