ghsa-qmjf-wc2h-6x3q
Vulnerability from github
Published
2024-05-29 18:40
Modified
2025-01-21 18:30
Severity ?
6.3 (Medium) - CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N
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
Show details on source website

To clipboard 

{
   affected: [
      {
         package: {
            ecosystem: "PyPI",
            name: "nautobot",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "1.3.0",
                  },
                  {
                     fixed: "1.6.23",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
      },
      {
         package: {
            ecosystem: "PyPI",
            name: "nautobot",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "2.0.0",
                  },
                  {
                     fixed: "2.2.5",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
      },
   ],
   aliases: [
      "CVE-2024-36112",
   ],
   database_specific: {
      cwe_ids: [
         "CWE-280",
      ],
      github_reviewed: true,
      github_reviewed_at: "2024-05-29T18:40:56Z",
      nvd_published_at: "2024-05-28T23:15:17Z",
      severity: "MODERATE",
   },
   details: "### Impact\n_What kind of vulnerability is it? Who is impacted?_\n\nA 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. \n\nIn 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.\n\n### Patches\n_Has the problem been patched? What versions should users upgrade to?_\n\nFixed in Nautobot 1.6.23 and 2.2.5.\n\n### Workarounds\n_Is there a way for users to fix or remediate the vulnerability without upgrading?_\n\nThis vulnerability can be partially mitigated by removing `extras.view_dynamicgroup` permission from users; a full fix will require upgrading.\n\n### References\n_Are there any links users can visit to find out more?_\n\n- https://github.com/nautobot/nautobot/pull/5757\n- https://github.com/nautobot/nautobot/pull/5762",
   id: "GHSA-qmjf-wc2h-6x3q",
   modified: "2025-01-21T18:30:41Z",
   published: "2024-05-29T18:40:56Z",
   references: [
      {
         type: "WEB",
         url: "https://github.com/nautobot/nautobot/security/advisories/GHSA-qmjf-wc2h-6x3q",
      },
      {
         type: "ADVISORY",
         url: "https://nvd.nist.gov/vuln/detail/CVE-2024-36112",
      },
      {
         type: "WEB",
         url: "https://github.com/nautobot/nautobot/pull/5757",
      },
      {
         type: "WEB",
         url: "https://github.com/nautobot/nautobot/pull/5762",
      },
      {
         type: "WEB",
         url: "https://github.com/nautobot/nautobot/commit/3a63aa1327f943b2ac8452757ea2e4d403387ad6",
      },
      {
         type: "WEB",
         url: "https://github.com/nautobot/nautobot/commit/4d1ff2abe2775b0a6fb16e6d1d503a78226a6f8e",
      },
      {
         type: "PACKAGE",
         url: "https://github.com/nautobot/nautobot",
      },
      {
         type: "WEB",
         url: "https://github.com/pypa/advisory-database/tree/main/vulns/nautobot/PYSEC-2024-166.yaml",
      },
   ],
   schema_version: "1.4.0",
   severity: [
      {
         score: "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N",
         type: "CVSS_V3",
      },
   ],
   summary: "Nautobot dynamic-group-members doesn't enforce permission restrictions on member objects",
}


Log in or create an account to share your comment.

Security Advisory comment format.

This schema specifies the format of a comment related to a security advisory.

UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).



Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.