Advisory

GHSA-qmjf-wc2h-6x3q

Also known as: CVE-2024-36112, PYSEC-2024-166

Summary

Nautobot dynamic-group-members doesn't enforce permission restrictions on member objects

Details

Impact
_What kind of vulnerability is it? Who is impacted?_

A user with permissions to view Dynamic Group records (extras.view_dynamicgroup permission) can use the Dynamic Group detail UI view (/extras/dynamic-groups/<uuid>/) and/or the members REST API view (/api/extras/dynamic-groups/<uuid>/members/) to list the objects that are members of a given Dynamic Group.

In versions of Nautobot between 1.3.0 (where the Dynamic Groups feature was added) and 1.6.22 inclusive, and 2.0.0 through 2.2.4 inclusive, Nautobot fails to restrict these listings based on the member object permissions - for example a Dynamic Group of Device objects will list all Devices that it contains, regardless of the user's dcim.view_device permissions or lack thereof.

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

Fixed in Nautobot 1.6.23 and 2.2.5.

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

This vulnerability can be partially mitigated by removing extras.view_dynamicgroup permission from users; a full fix will require upgrading.

References
_Are there any links users can visit to find out more?_

  • https://github.com/nautobot/nautobot/pull/5757
  • https://github.com/nautobot/nautobot/pull/5762

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2024-05-29 18:40 UTC
Modified
2026-06-10 17:14 UTC

Affected packages and fixes

nautobot

PyPI · All systems

Affected

  • introduced 1.3.0, fixed 1.6.23 (ecosystem)

Fixed versions

1.6.23

Fix

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

nautobot

PyPI · All systems

Affected

  • introduced 2.0.0, fixed 2.2.5 (ecosystem)

Fixed versions

2.2.5

Fix

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

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