CVE-2024-36112

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

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.

CVE-2024-36112 has a CVSS score of 6.3 (Medium). The vector is network-reachable, low 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.23, 2.2.5); upgrading removes the vulnerable code path.

Kodem intelligence

Has the problem been patched? What versions should users upgrade to?

Fixed in Nautobot 1.6.23 and 2.2.5.

1. What is CVE-2024-36112? CVE-2024-36112 is a medium-severity security vulnerability in nautobot (pip), affecting versions >= 1.3.0, < 1.6.23. It is fixed in 1.6.23, 2.2.5.
2. How severe is CVE-2024-36112? CVE-2024-36112 has a CVSS score of 6.3 (Medium). 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-2024-36112? nautobot (pip) versions >= 1.3.0, < 1.6.23 is affected.
4. Is there a fix for CVE-2024-36112? Yes. CVE-2024-36112 is fixed in 1.6.23, 2.2.5. Upgrade to this version or later.
5. Is CVE-2024-36112 exploitable, and should I be worried? Whether CVE-2024-36112 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-2024-36112 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-2024-36112?
   • Upgrade nautobot to 1.6.23 or later
   • Upgrade nautobot to 2.2.5 or later