← Back
CVE-2024-36110

Cross-Site Scripting (XSS) in ansibleguy-webui (CVE-2024-36110)

Summary

cross-site scripting in ansibleguy-webui (CVE-2024-36110). Confidential information can be exposed externally. Mitigation: upgrade to `0.0.21` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2024-36110** has been found in ansibleguy-webui. Confidential information can be exposed externally. CVSS score: ?/10. What to do: upgrade ansibleguy-webui to **0.0.21** or later. If unsure, ask your IT team or search "ansibleguy-webui CVE-2024-36110" on the vendor's site.
CVE-2024-36110 (ansibleguy-webui) — CWE-79 / Attack vector: remote (network-reachable) Patched: `0.0.21` — 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
**Cross-site scripting (XSS)** (CWE-79) exists in ansibleguy-webui.
📍 Affected scope
ansibleguy-webui — .
🔥 Severity
Severity: ?. Confidential information can be exposed externally
🔧 How to fix
Update to **0.0.21**.
🛡️ 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 'ansibleguy-webui' .` 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. 1
    Identify exposure identify
    grep -r 'ansibleguy-webui' . | grep -v node_modules

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

  2. 6
    Apply patch patch
    Upgrade ansibleguy-webui to 0.0.21

    ステージング環境で 0.0.21 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。

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

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

Affected packages

PyPI ansibleguy-webui
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.0.21"}]}]

References

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →