Loading vulnerability…
ZenML Server in the ZenML Python package before 0.46.7 contains an authorization flaw in the REST API endpoint /api/v1/users/{user_name_or_id}/activate. The endpoint improperly allows account activation and password setting based on knowledge of a valid username together with a new password supplied in the request body, without sufficient authentication or authorization checks. As a result, a remote attacker can target an existing user account and activate or take control of it by invoking the activation workflow directly. Patched versions were released in multiple supported branches: 0.42.2, 0.43.1, 0.44.4, and 0.46.7.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository provides a proof-of-concept (PoC) and an advanced exploit for CVE-2024-25723, a critical vulnerability in ZenML (versions below 0.46.7, except for certain patched versions). The exploit allows an attacker to reset the password of any user account by sending a crafted HTTP PUT request to the /api/v1/users/{username}/activate endpoint. The advanced exploit script (advanced-exploit-CVE-2024-25723.py) first checks if the target ZenML server is vulnerable by querying the /api/v1/info endpoint for its version. If vulnerable, it attempts to brute-force common usernames (from common-usernames.txt) and reset their passwords to a known value, effectively allowing account takeover. The repository contains three files: a README.md with detailed instructions and context, the main Python exploit script, and a list of common usernames. The exploit is network-based and targets ZenML servers accessible over HTTP(S).
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.