← Back
CVE-2024-45053
Vulnerability in ethyca-fides (CVE-2024-45053)
Summary
vulnerability in ethyca-fides (CVE-2024-45053). Successful exploitation can lead to full system takeover. Exploitable via `PUT /api/v1/messaging/templates/`. Mitigation: upgrade to `2.44.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2024-45053** has been found in ethyca-fides.
Attackers can target a specific entry point like `PUT /api/v1/messaging/templates/` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: ?/10.
What to do: upgrade ethyca-fides to **2.44.0** or later.
If unsure, ask your IT team or search "ethyca-fides CVE-2024-45053" on the vendor's site.
CVE-2024-45053 (ethyca-fides) — CWE-1336 /
Attack vector: remote (network-reachable) / no user interaction
Attack surface: PUT /api/v1/messaging/templates/ / PUT /api/v1/messaging/templates/autogenerated-mes_ce649254-a90b-4073-ae12-19365006422 / `Owner` / `Contributor`
Patched: `2.44.0` — 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** (CWE-1336) exists in ethyca-fides. Attackers reach the vulnerable code path via `PUT /api/v1/messaging/templates/` without authentication.
📍 Affected scope
ethyca-fides — . Attack surface: PUT /api/v1/messaging/templates/ / PUT /api/v1/messaging/templates/autogenerated-mes_ce649254-a90b-4073-ae12-19365006422 / `Owner` / `Contributor`.
🔥 Severity
Severity: ?. Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **2.44.0**.
🛡️ 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/messaging/templates/` requests with malformed payloads or SQL meta-characters. Run `grep -r 'ethyca-fides' .` 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
-
1Identify exposure identify
grep -r 'ethyca-fides' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `ethyca-fides` を grep し、稼働しているサービス・バージョンを把握する。
-
3Hunt for indicators of compromise detect
grep 'PUT /api/v1/messaging/templates/' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで `PUT /api/v1/messaging/templates/` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
-
6Apply patch patch
Upgrade ethyca-fides to 2.44.0ステージング環境で 2.44.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Replay attack against PUT /api/v1/messaging/templates/ on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
ethyca-fides
[{"type":"ECOSYSTEM","events":[{"introduced":"2.19.0"},{"fixed":"2.44.0"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2024-45053
- advisory https://github.com/advisories/GHSA-c34r-238x-f7qx
- package https://github.com/ethyca/fides
- package https://pypi.org/project/ethyca-fides
- web https://github.com/ethyca/fides/security/advisories/GHSA-c34r-238x-f7qx
- web https://github.com/ethyca/fides/commit/829cbd9cb5ef9c814fbac1ed6800e8d939d359c5