Categories
CVE-2021-41088

Vulnerability in github.com/elves/elvish (CVE-2021-41088)

Summary

Vulnerability in github.com/elves/elvish (CVE-2021-41088). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 0.14.0 or later.

Original description

The description as published by the source.

Impact

Elvish's backend for the experimental web UI (started by elvish -web) hosts an endpoint that allows executing the code sent from the web UI.

The backend does not check the origin of requests correctly. As a result, if the user has the web UI backend open and visits a compromised or malicious website, the website can send arbitrary code to the endpoint in localhost.

Patches

All Elvish releases since 0.14.0 no longer include the experimental web UI, although it is still possible for the user to build a version from source that includes it.

The issue can be patched for previous versions by removing the web UI (found in web, pkg/web or pkg/prog/web, depending on the exact version).

Workarounds

Do not use the experimental web UI.

For more information

If you have any questions or comments about this advisory, please email xiaqqaix@gmail.com.

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2021-41088 has been found in github.com/elves/elvish.
Successful exploitation can lead to full system takeover.
What to do: upgrade github.com/elves/elvish to 0.14.0 or later.
If unsure, ask your IT team or search "github.com/elves/elvish CVE-2021-41088" on the vendor's site.

CVE-2021-41088 (github.com/elves/elvish) — CWE-346
Attack vector: remote (network-reachable)
Patched: 0.14.0 — apply immediately
Workaround: Do not use the experimental web UI.
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-346) exists in github.com/elves/elvish.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/elves/elvish.

🔥 Severity

Severity: ?. Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 0.14.0.

🛡️ Workaround

Workaround: Do not use the experimental web UI.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/elves/elvish' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'github.com/elves/elvish' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/elves/elvish を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply temporary workaround mitigate
    Do not use the experimental web UI.

    パッチが適用されるまでの応急処置として、Do not use the experimental web UI. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch
    Upgrade github.com/elves/elvish to 0.14.0

    ステージング環境で 0.14.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Go github.com/elves/elvish
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.14.0"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details