Advisory

GHSA-vf5m-xrhm-v999

Also known as: CVE-2023-51649, PYSEC-2023-287

Summary

Nautobot missing object-level permissions enforcement when running Job Buttons

Details

Impact

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 (/extras/job-button/<uuid>/run/) The effect is that a user with permissions to run even a single Job can actually run all configured JobButton Jobs.

> Not all Jobs can be configured as JobButtons; only those implemented as subclasses of JobButtonReceiver can be used in this way, so this vulnerability only applies specifically to JobButtonReceiver subclasses.

Additionally, although the documentation states that both extras.run_job permission and extras.run_jobbutton permission must be granted to a user in order to run Jobs via JobButton, the extras.run_jobbutton permission is not actually enforced by the view code, only by the UI by disabling the button from being clicked normally. Furthermore, the extras.run_jobbutton permission never prevented invoking Jobs (including JobButtonReceiver subclasses) via the normal "Job Run" UI, so after some discussion, we've decided that the extras.run_jobbutton permission is redundant, and as it never achieved its stated/documented purpose, the fixes below will remove the UI check for extras.run_jobbutton and all other references to the extras.run_jobbutton permission, rather than adding enforcement of this previously unenforced permission.

Patches
_Has the problem been patched? What versions should users upgrade to?_

Fix will be available in Nautobot 1.6.8 (https://github.com/nautobot/nautobot/pull/4995) and 2.1.0 (https://github.com/nautobot/nautobot/pull/4993)

Workarounds
_Is there a way for users to fix or remediate the vulnerability without upgrading?_

Partial mitigation can be achieved by auditing JobButtonReceiver subclasses defined in the system and restricting which users are permitted to create or edit JobButton records.

References

  • https://github.com/nautobot/nautobot/issues/4988
  • https://github.com/nautobot/nautobot/pull/4993
  • https://github.com/nautobot/nautobot/pull/4995

Severity

Low Basis: The source's own band: LOW

Dates

Published
2023-12-22 19:51 UTC
Modified
2026-06-09 13:15 UTC

Affected packages and fixes

nautobot

PyPI · All systems

Affected

  • introduced 1.5.14, fixed 1.6.8 (ecosystem)

Fixed versions

1.6.8

Fix

  • Fixed version 1.6.8
    pip install --upgrade nautobot==1.6.8

nautobot

PyPI · All systems

Affected

  • introduced 2.0.0, fixed 2.1.0 (ecosystem)

Fixed versions

2.1.0

Fix

  • Fixed version 2.1.0
    pip install --upgrade nautobot==2.1.0

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences