CVE-2024-25723
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedZenML Server in the ZenML machine learning package before 0.46.7 for Python allows remote privilege escalation because the /api/v1/users/{user_name_or_id}/activate REST API endpoint allows access on the basis of a valid username along with a new password in the request body. These are also patched versions: 0.44.4, 0.43.1, and 0.42.2.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe ZenML Server /api/v1/users/{user_name_or_id}/activate endpoint allows remote privilege escalation by accepting a valid username along with a new password in the request body without requiring proper authentication. An unauthenticated attacker can reset any user's password and take over their account, including administrative accounts.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 0.42.2>= 0.44.0, < 0.44.4>= 0.45.0, < 0.46.7= 0.43.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the installed ZenML versionRun `zenml version` or check the Python package version with `pip show zenml`Affected if The version is < 0.42.2, = 0.43.0, >= 0.44.0 and < 0.44.4, or >= 0.45.0 and < 0.46.7
-
Confirm the ZenML server is runningCheck for running processes: `ps aux | grep zenml` or check if the server API is listening on its port (default 8080) with `netstat -tlnp | grep 8080`Affected if The server is running and the version is in the affected range above
-
Verify the activation endpoint is exposedAttempt a GET request to `http://<server>/api/v1/users/{任意用户名}/activate` without providing authentication credentialsAffected if The endpoint returns a valid HTTP response (rather than 401/403) indicating it is accessible without authentication
-
Check for recent authentication logsReview server logs for unauthenticated or failed login attempts to the `/activate` endpoint using `grep -i activate /var/log/zenml/*.log` or equivalent log locationAffected if Unauthenticated requests to the activation endpoint appear in logs, confirming the vulnerability is accessible
You are affected if the ZenML server is running with a version in the vulnerable range AND the activation endpoint is accessible without authentication.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped0.42.20.44.40.46.7
Upgrade ZenML to version 0.46.7 or later (or to patched versions 0.44.4, 0.43.1, or 0.42.2). The fix should enforce proper authentication and authorization checks before allowing password changes on the activation endpoint.
0.46.7 (or latest 0.46.x release)
- Check current ZenML version using: pip show zenml or zenml version
- Upgrade to the fixed version 0.46.7 using: pip install zenml==0.46.7
- Verify the upgrade was successful by running: zenml version
- Ensure the server is restarted after upgrading to load the patched code
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-25723 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-25723 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data