-
Notifications
You must be signed in to change notification settings - Fork 20
Description
Vulnerable Library - flask-3.1.0-py3-none-any.whl
A simple framework for building complex web applications.
Library home page: https://files.pythonhosted.org/packages/af/47/93213ee66ef8fae3b93b3e29206f6b251e65c97bd91d8e1c5596ef15af0a/flask-3.1.0-py3-none-any.whl
Path to dependency file: /Pi-CryptoConnect-Xtreme/requirements.txt
Path to vulnerable library: /Pi-CryptoConnect-Xtreme/requirements.txt
Found in HEAD commit: 2ed3e6d266405677eb45c15a472c288b604a1cad
Vulnerabilities
| Vulnerability | Severity | Dependency | Type | Fixed in (flask version) | Remediation Possible** | |
|---|---|---|---|---|---|---|
| CVE-2025-47278 | 2.3 | flask-3.1.0-py3-none-any.whl | Direct | 3.1.1 | ❌ |
**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation
Details
CVE-2025-47278
Vulnerable Library - flask-3.1.0-py3-none-any.whl
A simple framework for building complex web applications.
Library home page: https://files.pythonhosted.org/packages/af/47/93213ee66ef8fae3b93b3e29206f6b251e65c97bd91d8e1c5596ef15af0a/flask-3.1.0-py3-none-any.whl
Path to dependency file: /Pi-CryptoConnect-Xtreme/requirements.txt
Path to vulnerable library: /Pi-CryptoConnect-Xtreme/requirements.txt
Dependency Hierarchy:
- ❌ flask-3.1.0-py3-none-any.whl (Vulnerable Library)
Found in HEAD commit: 2ed3e6d266405677eb45c15a472c288b604a1cad
Found in base branch: main
Vulnerability Details
Flask is a web server gateway interface (WSGI) web application framework. In Flask 3.1.0, the way fallback key configuration was handled resulted in the last fallback key being used for signing, rather than the current signing key. Signing is provided by the "itsdangerous" library. A list of keys can be passed, and it expects the last (top) key in the list to be the most recent key, and uses that for signing. Flask was incorrectly constructing that list in reverse, passing the signing key first. Sites that have opted-in to use key rotation by setting "SECRET_KEY_FALLBACKS" care likely to unexpectedly be signing their sessions with stale keys, and their transition to fresher keys will be impeded. Sessions are still signed, so this would not cause any sort of data integrity loss. Version 3.1.1 contains a patch for the issue.
Publish Date: 2025-05-13
URL: CVE-2025-47278
CVSS 3 Score Details (2.3)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: High
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: Low
Suggested Fix
Type: Upgrade version
Origin: GHSA-4grg-w6v8-c28g
Release Date: 2025-05-13
Fix Resolution: 3.1.1
Step up your Open Source Security Game with Mend here