← Back
GHSA-vcv2-r9jh-99m5
OS Command Injection in agentic-flow (GHSA-vcv2-r9jh-99m5)
Summary
OS command injection in agentic-flow (GHSA-vcv2-r9jh-99m5). Risk of unauthorized operations or information disclosure. Exploitable via ``agent``. Mitigation: upgrade to `2.0.14` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **GHSA-vcv2-r9jh-99m5** has been found in agentic-flow.
Attackers can target a specific entry point like ``agent`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade agentic-flow to **2.0.14** or later.
If unsure, ask your IT team or search "agentic-flow GHSA-vcv2-r9jh-99m5" on the vendor's site.
GHSA-vcv2-r9jh-99m5 (agentic-flow) — CWE-78 /
Attack surface: `agent` / `task` / `name` / `language`
Patched: `2.0.14` — apply immediately
Workaround: Upgrade to `agentic-flow >= 2.0.14`.
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
**OS command injection** (CWE-78) exists in agentic-flow. Attackers reach the vulnerable code path via ``agent`` without authentication.
📍 Affected scope
agentic-flow — . Attack surface: `agent` / `task` / `name` / `language`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **2.0.14**.
🛡️ Workaround
Workaround: Upgrade to `agentic-flow >= 2.0.14`.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'agentic-flow' .` 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 'agentic-flow' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `agentic-flow` を grep し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
Upgrade to `agentic-flow >= 2.0.14`.パッチが適用されるまでの応急処置として、Upgrade to `agentic-flow >= 2.0.14`. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade agentic-flow to 2.0.14ステージング環境で 2.0.14 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
agentic-flow
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.0.14"}]}]
References
- web https://github.com/ruvnet/agentic-flow/security/advisories/GHSA-vcv2-r9jh-99m5
- web https://github.com/ruvnet/agentic-flow/issues/169
- web https://github.com/ruvnet/ruflo/issues/2414
- web https://github.com/ruvnet/agentic-flow/pull/170
- web https://github.com/ruvnet/ruflo/pull/2415
- web https://github.com/ruvnet/ruflo/releases/tag/v3.12.4
- web https://www.npmjs.com/package/agentic-flow/v/2.0.14
- web https://github.com/advisories/GHSA-vcv2-r9jh-99m5