← Back
GHSA-8cp3-qxj6-px34
SSRF (Server-Side Request Forgery) in utcp-http (GHSA-8cp3-qxj6-px34)
Summary
SSRF in utcp-http (GHSA-8cp3-qxj6-px34). Risk of unauthorized operations or information disclosure. Exploitable via ``tokenUrl``. Mitigation: upgrade to `1.1.4` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **GHSA-8cp3-qxj6-px34** has been found in utcp-http.
Attackers can target a specific entry point like ``tokenUrl`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade utcp-http to **1.1.4** or later.
If unsure, ask your IT team or search "utcp-http GHSA-8cp3-qxj6-px34" on the vendor's site.
GHSA-8cp3-qxj6-px34 (utcp-http) — CWE-918 /
Attack surface: `tokenUrl` / `client_id` / `client_secret` / `HttpCallTemplate`
Patched: `1.1.4` — 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
**SSRF** (CWE-918) exists in utcp-http. Attackers reach the vulnerable code path via ``tokenUrl`` without authentication.
📍 Affected scope
utcp-http — . Attack surface: `tokenUrl` / `client_id` / `client_secret` / `HttpCallTemplate`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **1.1.4**.
🛡️ 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 'utcp-http' .` 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 'utcp-http' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `utcp-http` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade utcp-http to 1.1.4ステージング環境で 1.1.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
utcp-http
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.4"}]}]