Vulnerability in zenml (CVE-2024-2035)

Summary

vulnerability in zenml (CVE-2024-2035). Data can be tampered with by attackers. Exploitable via `PUT /api/v1/users/id`. Mitigation: upgrade to `b95f083efffa56831cd41d8ed536aeb0b6038fa3, 0.56.2` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2024-2035** has been found in zenml. Attackers can target a specific entry point like `PUT /api/v1/users/id` over the network to misuse the product. Data can be tampered with by attackers. CVSS score: ?/10. What to do: upgrade zenml to **b95f083efffa56831cd41d8ed536aeb0b6038fa3, 0.56.2** or later. If unsure, ask your IT team or search "zenml CVE-2024-2035" on the vendor's site.

CVE-2024-2035 (zenml) — Attack vector: remote (network-reachable) / no user interaction Attack surface: PUT /api/v1/users/id / `active` Patched: `b95f083efffa56831cd41d8ed536aeb0b6038fa3, 0.56.2` — apply immediately Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs. Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

**A vulnerability** (unclassified) exists in zenml. Attackers reach the vulnerable code path via `PUT /api/v1/users/id` without authentication.

📍 Affected scope

zenml — . Attack surface: PUT /api/v1/users/id / `active`.

🔥 Severity

Severity: ?. Data can be tampered with by attackers

🔧 How to fix

Update to **b95f083efffa56831cd41d8ed536aeb0b6038fa3, 0.56.2**.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual `PUT /api/v1/users/id` requests with malformed payloads or SQL meta-characters. Run `grep -r 'zenml' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response Actions (7 steps)

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
grep -r 'zenml' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `zenml` を grep し、稼働しているサービス・バージョンを把握する。
3
Hunt for indicators of compromise detect
```
grep 'PUT /api/v1/users/id' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'
```
アクセスログで `PUT /api/v1/users/id` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
6
Apply patch patch
```
Upgrade zenml to b95f083efffa56831cd41d8ed536aeb0b6038fa3, 0.56.2
```
ステージング環境で b95f083efffa56831cd41d8ed536aeb0b6038fa3, 0.56.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
7
Post-deployment verification verify
```
Replay attack against PUT /api/v1/users/id on staging to confirm patch closes the vector
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

PyPI zenml

[{"repo":"https:\/\/github.com\/zenml-io\/zenml","type":"GIT","events":[{"introduced":"0"},{"fixed":"b95f083efffa56831cd41d8ed536aeb0b6038fa3"},{"fixed":"b95f083efffa56831cd41d8ed536aeb0b6038fa3"}]},{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.56.2"}]}]