← Back
CVE-2024-32979

Cross-Site Scripting (XSS) in nautobot (CVE-2024-32979)

Summary

cross-site scripting in nautobot (CVE-2024-32979). Data can be tampered with by attackers. Mitigation: upgrade to `2.2.3` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2024-32979** has been found in nautobot. Data can be tampered with by attackers. CVSS score: ?/10. What to do: upgrade nautobot to **2.2.3** or later. If unsure, ask your IT team or search "nautobot CVE-2024-32979" on the vendor's site.
CVE-2024-32979 (nautobot) — CWE-79 / Attack vector: remote (network-reachable) / unauthenticated Patched: `2.2.3` — apply immediately Workaround: No workaround has been identified 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 nautobot.
📍 Affected scope
nautobot — .
🔥 Severity
Severity: ?. Data can be tampered with by attackers
🔧 How to fix
Update to **2.2.3**.
🛡️ Workaround
Workaround: No workaround has been identified
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'nautobot' .` 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 'nautobot' . | grep -v node_modules

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

  2. 5
    Apply temporary workaround mitigate
    No workaround has been identified

    パッチが適用されるまでの応急処置として、No workaround has been identified を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 6
    Apply patch patch
    Upgrade nautobot to 2.2.3

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

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

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

Affected packages

PyPI nautobot
[{"type":"ECOSYSTEM","events":[{"introduced":"2.0.0"},{"fixed":"2.2.3"}]}]

References

🍪 About cookies

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

Details →