CVE-2023-50263

Workarounds

No workaround other than applying the patches included in https://github.com/nautobot/nautobot/pull/4959/files (2.0.x) or https://github.com/nautobot/nautobot/pull/4964/files (1.6.x)

References

• https://github.com/victor-o-silva/db_file_storage/blob/master/db_file_storage/views.py

In Nautobot 1.x and 2.0.x, 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.

It was reported by @kircheneer that 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.

A critical operation is accessible without requiring any authentication. Typical impact: any user can invoke the privileged function.

CVE-2023-50263 has a CVSS score of 3.7 (Low). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.6.7, 2.0.6); upgrading removes the vulnerable code path.

Kodem intelligence

Fixes will be included in Nautobot 1.6.7 and Nautobot 2.0.6.

1. What is CVE-2023-50263? CVE-2023-50263 is a low-severity missing authentication for critical function vulnerability in nautobot (pip), affecting versions >= 1.1.0, < 1.6.7. It is fixed in 1.6.7, 2.0.6. A critical operation is accessible without requiring any authentication.
2. How severe is CVE-2023-50263? CVE-2023-50263 has a CVSS score of 3.7 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of nautobot are affected by CVE-2023-50263? nautobot (pip) versions >= 1.1.0, < 1.6.7 is affected.
4. Is there a fix for CVE-2023-50263? Yes. CVE-2023-50263 is fixed in 1.6.7, 2.0.6. Upgrade to this version or later.
5. Is CVE-2023-50263 exploitable, and should I be worried? Whether CVE-2023-50263 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2023-50263 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2023-50263?
   • Upgrade nautobot to 1.6.7 or later
   • Upgrade nautobot to 2.0.6 or later