Vulnerability in python-werkzeug (UBUNTU-CVE-2024-49767)

Summary

vulnerability in python-werkzeug (UBUNTU-CVE-2024-49767). Risk of unauthorized operations or information disclosure. Exploitable via ``werkzeug.formparser.MultiPartParser``. Mitigation: upgrade to `2.0.2+dfsg1-1ubuntu0.22.04.3` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **UBUNTU-CVE-2024-49767** has been found in python-werkzeug. Attackers can target a specific entry point like ``werkzeug.formparser.MultiPartParser`` over the network to misuse the product. Risk of unauthorized operations or information disclosure. CVSS score: ?/10. What to do: upgrade python-werkzeug to **2.0.2+dfsg1-1ubuntu0.22.04.3** or later. If unsure, ask your IT team or search "python-werkzeug UBUNTU-CVE-2024-49767" on the vendor's site.

UBUNTU-CVE-2024-49767 (python-werkzeug) — Attack vector: remote (network-reachable) / unauthenticated / no user interaction Attack surface: `werkzeug.formparser.MultiPartParser` Patched: `2.0.2+dfsg1-1ubuntu0.22.04.3` — 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 python-werkzeug. Attackers reach the vulnerable code path via ``werkzeug.formparser.MultiPartParser`` without authentication.

📍 Affected scope

python-werkzeug — . Attack surface: `werkzeug.formparser.MultiPartParser`.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure

🔧 How to fix

Update to **2.0.2+dfsg1-1ubuntu0.22.04.3**.

🛡️ 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 request patterns matching this CVE's known IOCs. Run `grep -r 'python-werkzeug' .` 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 'python-werkzeug' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `python-werkzeug` を grep し、稼働しているサービス・バージョンを把握する。
6
Apply patch patch
```
Upgrade python-werkzeug to 2.0.2+dfsg1-1ubuntu0.22.04.3
```
ステージング環境で 2.0.2+dfsg1-1ubuntu0.22.04.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
7
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

Ubuntu:22.04:LTS python-werkzeug

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.0.2+dfsg1-1ubuntu0.22.04.3"}]}]

Ubuntu:22.04:LTS quart

[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]

Ubuntu:24.04:LTS python-werkzeug

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.0.1-3ubuntu0.2"}]}]

Ubuntu:24.04:LTS quart

[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]

Ubuntu:25.10 quart

[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]

Ubuntu:26.04:LTS quart

[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]

Vulnerability in python-werkzeug (UBUNTU-CVE-2024-49767)

Summary

AI summary snake-internal / snake-material-v2

Response Actions (7 steps)

Affected packages

References

🍪 About cookies