Vulnerability in runtimedev-link (GHSA-v63r-xv67-wj6q)

Summary

vulnerability in runtimedev-link (GHSA-v63r-xv67-wj6q). Risk of unauthorized operations or information disclosure. Exploitable via `POST /api/telemetry/poll-command`.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **GHSA-v63r-xv67-wj6q** has been found in runtimedev-link. Attackers can target a specific entry point like `POST /api/telemetry/poll-command` over the network to misuse the product. Risk of unauthorized operations or information disclosure. CVSS score: ?/10. What to do: apply the vendor's official patched release. If unsure, ask your IT team or search "runtimedev-link GHSA-v63r-xv67-wj6q" on the vendor's site.

GHSA-v63r-xv67-wj6q (runtimedev-link) — Attack surface: POST /api/telemetry/poll-command / `apiBase` / `command` / `execSync` 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 runtimedev-link. Attackers reach the vulnerable code path via `POST /api/telemetry/poll-command` without authentication.

📍 Affected scope

runtimedev-link — . Attack surface: POST /api/telemetry/poll-command / `apiBase` / `command` / `execSync`.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ 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 `POST /api/telemetry/poll-command` requests with malformed payloads or SQL meta-characters. Run `grep -r 'runtimedev-link' .` 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 'runtimedev-link' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `runtimedev-link` を grep し、稼働しているサービス・バージョンを把握する。
3
Hunt for indicators of compromise detect
```
grep 'POST /api/telemetry/poll-command' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'
```
アクセスログで `POST /api/telemetry/poll-command` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
7
Post-deployment verification verify
```
Replay attack against POST /api/telemetry/poll-command on staging to confirm patch closes the vector
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

npm runtimedev-link

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

References

advisory https://github.com/advisories/GHSA-v63r-xv67-wj6q
package https://www.npmjs.com/package/runtimedev-link/v/1.0.13
package https://www.npmjs.com/package/runtimedev-link/v/1.0.12
package https://www.npmjs.com/package/runtimedev-link/v/1.0.14
package https://www.npmjs.com/package/runtimedev-link/v/1.0.2
package https://www.npmjs.com/package/runtimedev-link/v/1.0.11
package https://www.npmjs.com/package/runtimedev-link/v/1.0.10
package https://www.npmjs.com/package/runtimedev-link/v/1.0.8
package https://www.npmjs.com/package/runtimedev-link/v/1.0.3
package https://www.npmjs.com/package/runtimedev-link/v/1.0.5
package https://www.npmjs.com/package/runtimedev-link/v/1.0.1
package https://www.npmjs.com/package/runtimedev-link/v/1.0.0
package https://www.npmjs.com/package/runtimedev-link/v/1.0.6
package https://www.npmjs.com/package/runtimedev-link/v/1.0.9