CVE-2024-36112: Nautobot dynamic-group-members doesn't enforce permission restrictions on member objects
Impact What kind of vulnerability is it? Who is impacted? A user with permissions to view Dynamic Group records (extras.viewdynamicgroup permission) can use the Dynamic Group detail UI view (/extras/dynamic-groups/ /) and/or the members REST API view (/api/extras/dynamic-groups/ /members/) to list the objects that are members of a given Dynamic Group.
Published May 29, 2024 · Updated Jan 21, 2025
Affected packages
nautobot
- Ecosystem
- PyPI
- Affected
- >= 1.3.0, < 1.6.23
- Fixed in
- 1.6.23
- Check
pip show nautobot
nautobot
- Ecosystem
- PyPI
- Affected
- >= 2.0.0, < 2.2.5
- Fixed in
- 2.2.5
- Check
pip show nautobot
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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
References
- https://github.com/nautobot/nautobot/security/advisories/GHSA-qmjf-wc2h-6x3q
- https://nvd.nist.gov/vuln/detail/CVE-2024-36112
- https://github.com/nautobot/nautobot/pull/5757
- https://github.com/nautobot/nautobot/pull/5762
- https://github.com/nautobot/nautobot/commit/3a63aa1327f943b2ac8452757ea2e4d403387ad6
- https://github.com/nautobot/nautobot/commit/4d1ff2abe2775b0a6fb16e6d1d503a78226a6f8e
- https://github.com/pypa/advisory-database/tree/main/vulns/nautobot/PYSEC-2024-166.yaml
- https://github.com/advisories/GHSA-qmjf-wc2h-6x3q
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More PyPI vulnerabilities
All PyPI entriesCVE-2026-83801
Nautobot: Stored cross-site scripting (XSS) in object create/edit form help text
medium5.4Sep 22, 2026CVE-2026-83805
Nautobot: Authorization bypass in approval workflow REST API allows self-approval and unauthorized activation of scheduled jobs
medium6.4Sep 22, 2026CVE-2026-44794
Nautobot: REST API permits creation of GenericForeignKey references to objects that the user should not be able to reference
medium5.4May 13, 2026CVE-2026-44796
Nautobot: Object bulk rename UI actions vulnerable to denial of service by crafted regular expression (REDoS)
medium6.5May 13, 2026CVE-2026-44797
Nautobot: Webhook definitions could be used for server-side request forgery (SSRF)
high8.5May 13, 2026CVE-2026-44798
Nautobot: GitRepository.current_head field should not be writable through REST API
high7.1May 13, 2026
