CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
4.8 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in zenml-io ZenML up to 0.56.1. Affected by this issue is some unknown functionality of the component JWT Token Handler. The manipulation leads to session fixiation. This vulnerability is handled as CVE-2024-2260. The attack may be launched remotely. There is no exploit available. It is recommended to upgrade the affected component. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Details
A vulnerability classified as critical was found in zenml-io ZenML up to 0.56.1. Affected by this vulnerability is some unknown functionality of the component JWT Token Handler. The manipulation with an unknown input leads to a session fixiation vulnerability. The CWE definition for the vulnerability is CWE-384. Authenticating a user, or otherwise establishing a new user session, without invalidating any existing session identifier gives an attacker the opportunity to steal authenticated sessions. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
A session fixation vulnerability exists in the zenml-io/zenml application, where JWT tokens used for user authentication are not invalidated upon logout. This flaw allows an attacker to bypass authentication mechanisms by reusing a victim's JWT token.
The advisory is shared at huntr.com. This vulnerability is known as CVE-2024-2260 since 03/07/2024. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available.
Upgrading to version 0.56.2 eliminates this vulnerability. Applying the patch 68bcb3ba60cba9729c9713a49c39502d40fb945e is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2024-1199). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.9VulDB Meta Temp Score: 4.8
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 4.2
NVD Vector: 🔍
CNA Base Score: 4.2
CNA Vector (huntr.dev): 🔍
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: Session fixiationCWE: CWE-384
CAPEC: 🔍
ATT&CK: 🔍
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: ZenML 0.56.2
Patch: 68bcb3ba60cba9729c9713a49c39502d40fb945e
Timeline
03/07/2024 🔍04/16/2024 🔍
04/16/2024 🔍
06/13/2025 🔍
Sources
Advisory: 68bcb3ba60cba9729c9713a49c39502d40fb945eStatus: Confirmed
CVE: CVE-2024-2260 (🔍)
GCVE (CVE): GCVE-0-2024-2260
GCVE (VulDB): GCVE-100-260857
EUVD: 🔍
Entry
Created: 04/16/2024 08:13 AMUpdated: 06/13/2025 08:34 AM
Changes: 04/16/2024 08:13 AM (66), 05/23/2024 08:24 AM (1), 04/06/2025 02:00 AM (4), 06/13/2025 02:41 AM (12), 06/13/2025 08:34 AM (1)
Complete: 🔍
Cache ID: 18:17C:40
No comments yet. Languages: en.
Please log in to comment.