# CVE-2023-51649: Nautobot missing object-level permissions enforcement when running Job Buttons

> Users with permission to run any job can execute all configured JobButton jobs due to missing object-level permission checks in Nautobot.

- **Severity:** Low 3.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Dec 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-vf5m-xrhm-v999, PYSEC-2023-287

## What is CVE-2023-51649?

CVE-2023-51649 is a low-severity missing authorization vulnerability in nautobot, published on 22 Dec 2023. Any signed-in user can exploit it over the network, 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. When submitting a Job to run via a Job Button, only the model-level `extras.run_job` permission is checked (i.e., does the user have permission to run Jobs in general). Object-level permissions (i.e., does the user have permission to run this specific Job?) are not enforced by the URL/view used in this case. A user with permissions to run even a single Job can actually run all configured JobButton Jobs. Fix will be available in Nautobot 1.6.8 and 2.1.0

Weakness: CWE-863 (Incorrect Authorization)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `nautobot` | PyPI | From 1.5.14 | 1.6.8, 2.1.0 |
| `nautobot` | PyPI | From 1.5.14 | 1.6.8 |
| `nautobot` | PyPI | From 1.5.14 | 1.6.8 |
| `nautobot` | PyPI | From 2.0.0 | 2.1.0 |
| `nautobot` | PyPI | From 2.0.0 | 2.1.0 |

Products: Networktocode Nautobot.

## How do I fix CVE-2023-51649?

Upgrade nautobot to a fixed version for your release line: 1.6.8 or 2.1.0.

## Is CVE-2023-51649 being exploited?

There is no known exploitation of CVE-2023-51649 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-51649 and fix it if it is affected.

What it is: CVE-2023-51649 is a low-severity missing authorization vulnerability in nautobot, published on 22 Dec 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-51649 in the wild and no public exploit code.

Affected packages and fixed versions:
- nautobot (PyPI): affected from 1.5.14; fixed in 1.6.8, 2.1.0
- nautobot (PyPI): affected from 1.5.14; fixed in 1.6.8
- nautobot (PyPI): affected from 1.5.14; fixed in 1.6.8
- nautobot (PyPI): affected from 2.0.0; fixed in 2.1.0
- nautobot (PyPI): affected from 2.0.0; fixed in 2.1.0

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-51649/ (Markdown: https://insights.sbomify.com/CVE-2023-51649/index.md)
```

## Sources

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

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