CVE intelligence and bounded remediation
CVE-2023-50263 — Networktocode Nautobot security vulnerability
Nautobot is a Network Source of Truth and Network Automation Platform built as a web application atop the Django Python framework with a PostgreSQL or MySQL database. In Nautobot 1.x and 2.0.x prior to 1.6.7 and 2.0.6, the URLs `/files/get/?name=...` and `/files/download/?name=...` are used to provide admin access to files that have been uploaded as part of a run request for a Job that has FileVar inputs. Under normal operation these files are ephemeral and are deleted once the Job in question runs. In the default implementation used in Nautobot, as provided by `django-db-file-storage`, these URLs do not by default require any user authentication to access; they should instead be restricted to only users who have permissions to view Nautobot's `FileProxy` model instances. Note that no URL mechanism is provided for listing or traversal of the available file `name` values, so in practice an unauthenticated user would have to guess names to discover arbitrary files for download, but if a user knows the file name/path value, they can access it without authenticating, so we are considering this a vulnerability. Fixes are included in Nautobot 1.6.7 and Nautobot 2.0.6. No known workaroun…
- Severity
- Medium
- CVSS
- 5.3 (3.1)
- Published
- 2023-12-12
- CISA KEV
- Not currently listed
- Ecosystem
- python/pypi
- Weaknesses
- CWE-200, CWE-306
Affected products
- networktocode / nautobot
Matched remediation archetype
Authentication bypass and missing authentication
This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.
Check exposure
- Map every affected endpoint and protocol path, including alternate ports, legacy routes, recovery flows, service accounts, and machine-to-machine access.
- Confirm which deployments enable the affected authentication mode and whether the interface is reachable from untrusted networks.
- Review session, token, credential, and proxy trust configuration without attempting account takeover.
Remediate safely
- Apply the supported fix and centralize fail-closed authentication before protected request handling.
- Remove default or embedded credentials, rotate affected secrets and sessions, and bind authentication decisions to the intended audience and channel.
- Add negative tests for alternate routes, malformed or absent credentials, recovery flows, and proxy-derived identity.
Authoritative sources
Complete CVE record and remediation plan
The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.