Sign in Sign up
JA · EN · FR
SecPulse
← Back
CVE-2024-29199

Information Disclosure in nautobot (CVE-2024-29199)

Summary

vulnerability in nautobot (CVE-2024-29199). Risk of unauthorized operations or information disclosure. Exploitable via ``EXEMPT_VIEW_PERMISSIONS``. Mitigation: upgrade to `2.1.9` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2024-29199** has been found in nautobot. Attackers can target a specific entry point like ``EXEMPT_VIEW_PERMISSIONS`` over the network to misuse the product. Risk of unauthorized operations or information disclosure. CVSS score: ?/10. What to do: upgrade nautobot to **2.1.9** or later. If unsure, ask your IT team or search "nautobot CVE-2024-29199" on the vendor's site.
CVE-2024-29199 (nautobot) — CWE-200 / Attack vector: remote (network-reachable) / unauthenticated / no user interaction Attack surface: `EXEMPT_VIEW_PERMISSIONS` Patched: `2.1.9` — apply immediately Workaround: Partial workaround: If your configuration includes a non-default value for `EXEMPT_VIEW_PERMISSIONS` (the Nautobot default is an empty list), reverting it to default will prevent exposure of Nautobot information to unauthenticated users via the endpo 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
**information disclosure** (CWE-200) exists in nautobot. Attackers reach the vulnerable code path via ``EXEMPT_VIEW_PERMISSIONS`` without authentication.
📍 Affected scope
nautobot — . Attack surface: `EXEMPT_VIEW_PERMISSIONS`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **2.1.9**.
🛡️ Workaround
Workaround: Partial workaround: If your configuration includes a non-default value for `EXEMPT_VIEW_PERMISSIONS` (the Nautobot default is an empty list), reverting it to default will prevent exposure of Nautobot information to unauthenticated users via the endpo
🔍 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 
    Partial workaround: If your configuration includes a non-default value for `EXEMPT_VIEW_PERMISSIONS` (the Nautobot default is an empty list), reverting it to default will prevent exposure of Nautobot information to unauthenticated users via the endpo

    パッチが適用されるまでの応急処置として、Partial workaround: If your configuration includes a non-default value for `EXEMPT_VIEW_PERMISSIONS` (the Nautobot default is an empty list), reverting it to default will prevent exposure of Nautobot information to unauthenticated users via the endpo を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 6
    Apply patch patch 
    Upgrade nautobot to 2.1.9

    ステージング環境で 2.1.9 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、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.1.9"}]}]

References

🍪 About cookies

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

Details →