CVE-2023-50263 Nautobot allows unauthenticated db-file-storage views
Unauthenticated attackers can access uploaded job files if they know the filename, leading to information disclosure in Nautobot.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2023-50263?
CVE-2023-50263 is a low-severity missing authorization vulnerability in nautobot, published on 12 Dec 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
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 workarounds are available other than applying the patches included in those versions.
Which versions are affected by CVE-2023-50263?
5 open source packages ship an affected version, including nautobot. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
nautobot PyPI | From 1.1.0 | 1.6.7, 2.0.6 |
nautobot PyPI | From 1.1.0 | 1.6.7 |
nautobot PyPI | From 1.1.0 | 1.6.7 |
nautobot PyPI | From 2.0.0 | 2.0.6 |
nautobot PyPI | From 2.0.0 | 2.0.6 |
Products include Networktocode Nautobot.
How do I fix CVE-2023-50263?
Upgrade nautobot to a fixed version for your release line: 1.6.7 or 2.0.6.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is CVE-2023-50263 being exploited?
There is no known exploitation of CVE-2023-50263 in the wild and no public exploit code.
Other vulnerabilities in nautobot
- CVE-2026-44797 Nautobot: Webhook definitions could be used for server-side request forgery (SSRF)
- CVE-2024-34707 Nautobot's BANNER_* configuration can be used to inject arbitrary HTML content into Nautobot pages
- CVE-2024-32979 Reflected Cross-site Scripting potential in all object list views in Nautobot
- CVE-2023-25657 Remote code execution in Jinja2 template rendering in Nautobot
- CVE-2026-44798 Nautobot: GitRepository.current_head field should not be writable through REST API
Sources
Also known as GHSA-75mc-3pjc-727q, PYSEC-2023-286.