# 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.

- **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Dec 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-75mc-3pjc-727q, PYSEC-2023-286

## 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.

Weakness: CWE-306 (Missing Authentication for Critical Functionality), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2023-50263?

5 open source packages ship an affected version, including nautobot. It affects 1 product.


| Package | Ecosystem | 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: 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.

## 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](https://insights.sbomify.com/CVE-2026-44797/): Nautobot: Webhook definitions could be used for server-side request forgery (SSRF) (high 8.5)
- [CVE-2024-34707](https://insights.sbomify.com/CVE-2024-34707/): Nautobot's BANNER_* configuration can be used to inject arbitrary HTML content into Nautobot pages (high 7.5)
- [CVE-2024-32979](https://insights.sbomify.com/CVE-2024-32979/): Reflected Cross-site Scripting potential in all object list views in Nautobot (high 7.5)
- [CVE-2023-25657](https://insights.sbomify.com/CVE-2023-25657/): Remote code execution in Jinja2 template rendering in Nautobot (high 7.5)
- [CVE-2026-44798](https://insights.sbomify.com/CVE-2026-44798/): Nautobot: GitRepository.current_head field should not be writable through REST API (high 7.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-50263 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2023-50263 in the wild and no public exploit code.

Affected packages and fixed versions:
- nautobot (PyPI): affected from 1.1.0; fixed in 1.6.7, 2.0.6
- nautobot (PyPI): affected from 1.1.0; fixed in 1.6.7
- nautobot (PyPI): affected from 1.1.0; fixed in 1.6.7
- nautobot (PyPI): affected from 2.0.0; fixed in 2.0.6
- nautobot (PyPI): affected from 2.0.0; fixed in 2.0.6

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-50263/ (Markdown: https://insights.sbomify.com/CVE-2023-50263/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-50263
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-50263
- OSV: https://osv.dev/vulnerability/CVE-2023-50263

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-50263/
Summaries are generated and may contain mistakes; the official description above is the record.