← Back
CVE-2024-34707
Cross-Site Scripting (XSS) in nautobot (CVE-2024-34707)
Summary
cross-site scripting in nautobot (CVE-2024-34707). Data can be tampered with by attackers. Exploitable via ``BANNER_TOP``. Mitigation: upgrade to `2.2.4` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2024-34707** has been found in nautobot.
Attackers can target a specific entry point like ``BANNER_TOP`` over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: ?/10.
What to do: upgrade nautobot to **2.2.4** or later.
If unsure, ask your IT team or search "nautobot CVE-2024-34707" on the vendor's site.
CVE-2024-34707 (nautobot) — CWE-79 /
Attack vector: remote (network-reachable)
Attack surface: `BANNER_TOP` / `BANNER_BOTTOM` / `BANNER_LOGIN` / `nautobot_config.py`
Patched: `2.2.4` — 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 nautobot. Attackers reach the vulnerable code path via ``BANNER_TOP`` without authentication.
📍 Affected scope
nautobot — . Attack surface: `BANNER_TOP` / `BANNER_BOTTOM` / `BANNER_LOGIN` / `nautobot_config.py`.
🔥 Severity
Severity: ?. Data can be tampered with by attackers
🔧 How to fix
Update to **2.2.4**.
🛡️ 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 '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
-
1Identify exposure identify
grep -r 'nautobot' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `nautobot` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade nautobot to 2.2.4ステージング環境で 2.2.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-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.4"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2024-34707
- advisory https://github.com/advisories/GHSA-r2hr-4v48-fjv3
- package https://github.com/nautobot/nautobot
- package https://pypi.org/project/nautobot
- web https://github.com/nautobot/nautobot/security/advisories/GHSA-r2hr-4v48-fjv3
- web https://github.com/nautobot/nautobot/pull/5697
- web https://github.com/nautobot/nautobot/pull/5698
- web https://github.com/nautobot/nautobot/commit/4f0a66bd6307bfe0e0acb899233e0d4ad516f51c
- web https://github.com/nautobot/nautobot/commit/f640aedc69c848d3d1be57f0300fc40033ff6423