CVE-2024-2213VulnerabilityPublished 6 Jun 2024Updated 21 Oct 2025

CVE-2024-2213: zenml-io/zenml · Unverified Password Change

Affects zenml-io/zenmlSource CVE Database V5

Not known to be exploited · CVSS 3.3 Low · fixed in 0.56.3 : update zenml-io/zenml when convenient.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.0 base score

3.3Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 0.56.3

CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 6 Jun 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
PyPIzenml`pkg:pypi/zenml`Other threats	Affected <=0.55.4	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-2213, European organizations should: 1) Immediately upgrade zenml-io/zenml installations to version 0.56.3 or later, where the vulnerability is fixed. 2) Implement strict session management controls, including session timeouts and detection of anomalous session activity, to reduce the risk of session hijacking. 3) Enforce multi-factor authentication (MFA) to strengthen user authentication beyond session tokens. 4) Monitor account activity logs for unusual password change attempts or session anomalies. 5) Educate users about the risks of session sharing and the importance of logging out from shared or public devices. 6) Consider network segmentation and access controls to limit exposure of zenml-io/zenml services to trusted users only. 7) Regularly audit and review user privileges to minimize the number of users with active sessions that could be exploited. 8) Integrate vulnerability scanning and patch management processes to ensure timely updates of open-source components like zenml-io/zenml.

Description

An issue was discovered in zenml-io/zenml versions up to and including 0.55.4. Due to improper authentication mechanisms, an attacker with access to an active user session can change the account password without needing to know the current password. This vulnerability allows for unauthorized account takeover by bypassing the standard password change verification process. The issue was fixed in version 0.56.3.

Impact

For European organizations, the impact of CVE-2024-2213 is primarily related to account integrity within the zenml-io/zenml platform. Unauthorized password changes can lead to account takeover, which may allow attackers to manipulate machine learning workflows, access sensitive project data, or disrupt operations. While confidentiality and availability are not directly affected, compromised accounts could be leveraged for further attacks or data manipulation, potentially undermining trust in ML pipelines. The requirement for an active session limits remote exploitation but raises concerns in environments where session hijacking or insider threats are possible. Organizations heavily reliant on zenml-io/zenml for MLOps may face operational risks and reputational damage if attackers exploit this vulnerability. The low CVSS score indicates limited severity, but the risk increases if attackers can gain session access through other means. European entities in sectors such as finance, healthcare, and manufacturing, which increasingly use ML workflows, should be vigilant. Failure to patch could result in unauthorized access to critical ML infrastructure and data integrity issues.

CWE-620Unverified Password Change (opens in a new tab)
Base weaknessOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
When setting a new password for a user, the product does not require knowledge of the original password, or using another form of authentication.
Architecture and Design
When prompting for a password change, force the user to provide the original password in addition to the new password.
Architecture and Design
Do not use "forgotten password" functionality. But if you must, ensure that you are only providing information to the actual user, e.g. by using an email address or challenge question that the legitimate user already provided in the past; do not allow the current user to change this identity information until the…
OWASP Cheat Sheets
Choosing and Using Security Questions (opens in a new tab)
Forgot Password (opens in a new tab)
Credential Stuffing Prevention (opens in a new tab)
Authentication (opens in a new tab)
Transport Layer Protection (opens in a new tab)
OWASP ASVS 4.0.3
V2.1.6 (opens in a new tab)
V2.2.3 (opens in a new tab)
V2.1.5 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 22 Oct 2025, 13:39 UTC

WeaknessesCWE-620

Technical details

References

Community reviews

Related threats