ghsa-j5hq-5jcr-xwx7
Vulnerability from github
Published
2024-11-20 18:23
Modified
2025-04-11 23:13
Severity ?
7.7 (High) - CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
Summary
github.com/rancher/steve's users can issue watch commands for arbitrary resources
Details

Impact

A vulnerability has been discovered in Steve API (Kubernetes API Translator) in which users can watch resources they are not allowed to access, when they have at least some generic permissions on the type. For example, a user who can get a single secret in a single namespace can get all secrets in every namespace.

During a watch request for a single ID, the following occurs: - In the case of a watch request for a single resource, Steve API will return a partition with the requested resource in it. In other cases, it will check the user's access when constructing partitions. - When a watch request for a single resource is issued, instead of using a client which impersonates the user making the request, Steve API will use the admin client, which can read all resources.

This allows any requester to see the contents of any object such as secret keys, signing certificates, API tokens.

Please consult the associated MITRE ATT&CK - Technique - Valid Accounts and MITRE ATT&CK - Technique - Container and Resource Discovery for further information about this category of attack.

Patches

To address this issue, the fix introduces a change in the behavior of the Steve API.

When issuing a watch request with an ID specified, the requester's permissions are now correctly honoured. This will deny events for objects the requester cannot actually access. Previously these events were returned unconditionally, allowing any requester to see the contents of any object.

Patched versions include the following commits:

| Branch | Commit | | -------- | ------- | | main | https://github.com/rancher/steve/commit/2175e090fe4b1e603a54e1cdc5148a2b1c11b4d9 | | release/v2.9 | https://github.com/rancher/steve/commit/6e30359c652333a49e229b2791c9b403d5ef81a9 | | release/v2.8 | https://github.com/rancher/steve/commit/c744f0b17b88ff5e2fcabc60841174d878ddc88e |

Workarounds

There are no workarounds for this issue. Users are recommended to upgrade, as soon as possible, to a version of Steve API/Rancher Manager which contains the fixes.

References

If you have any questions or comments about this advisory: - Reach out to the SUSE Rancher Security team for security-related inquiries. - Open an issue in the Rancher repository. - Verify with our support matrix and product support lifecycle.

Show details on source website

To clipboard 

{
  "affected": [
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/rancher/steve"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "0.0.0-20241029132712-2175e090fe4b"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2024-52280"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-200",
      "CWE-287"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2024-11-20T18:23:25Z",
    "nvd_published_at": "2025-04-11T12:15:14Z",
    "severity": "HIGH"
  },
  "details": "### Impact\nA vulnerability has been discovered in Steve API (Kubernetes API Translator) in which users can watch resources they are not allowed to access, when they have at least some generic permissions on the type. For example, a user who can get a single secret in a single namespace can get all secrets in every namespace.\n\nDuring a `watch` request for a single ID, the following occurs:\n- In the case of a watch request for a single resource, Steve API will return a partition with the requested resource in it. In other cases, it will check the user\u0027s access when constructing partitions.\n- When a watch request for a single resource is issued, instead of using a client which impersonates the user making the request, Steve API will use the admin client, which can read all resources.\n\nThis allows any requester to see the contents of any object such as secret keys, signing certificates, API tokens.\n\nPlease consult the associated  [MITRE ATT\u0026CK - Technique - Valid Accounts](https://attack.mitre.org/techniques/T1078/003/) and  [MITRE ATT\u0026CK - Technique - Container and Resource Discovery](https://attack.mitre.org/techniques/T1613/) for further information about this category of attack.\n\n### Patches\nTo address this issue, the fix introduces a change in the behavior of the Steve API.\n\nWhen issuing a `watch` request with an ID specified, the requester\u0027s permissions are now correctly honoured. This will deny events for objects the requester cannot actually access. Previously these events were returned unconditionally, allowing any requester to see the contents of any object.\n\nPatched versions include the following commits:\n\n| Branch    | Commit |\n| -------- | ------- |\n| main | https://github.com/rancher/steve/commit/2175e090fe4b1e603a54e1cdc5148a2b1c11b4d9 |\n| release/v2.9 | https://github.com/rancher/steve/commit/6e30359c652333a49e229b2791c9b403d5ef81a9 |\n| release/v2.8 | https://github.com/rancher/steve/commit/c744f0b17b88ff5e2fcabc60841174d878ddc88e |\n\n### Workarounds\nThere are no workarounds for this issue. Users are recommended to upgrade, as soon as possible, to a version of Steve API/Rancher Manager which contains the fixes.\n\n### References\nIf you have any questions or comments about this advisory:\n- Reach out to the [SUSE Rancher Security team](https://github.com/rancher/rancher/security/policy) for security-related inquiries.\n- Open an issue in the [Rancher](https://github.com/rancher/rancher/issues/new/choose) repository.\n- Verify with our [support matrix](https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/) and [product support lifecycle](https://www.suse.com/lifecycle/).",
  "id": "GHSA-j5hq-5jcr-xwx7",
  "modified": "2025-04-11T23:13:04Z",
  "published": "2024-11-20T18:23:25Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/rancher/steve/security/advisories/GHSA-j5hq-5jcr-xwx7"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-52280"
    },
    {
      "type": "WEB",
      "url": "https://github.com/rancher/steve/commit/2175e090fe4b1e603a54e1cdc5148a2b1c11b4d9"
    },
    {
      "type": "WEB",
      "url": "https://bugzilla.suse.com/show_bug.cgi?id=CVE-2024-52280"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/rancher/steve"
    },
    {
      "type": "WEB",
      "url": "https://pkg.go.dev/vuln/GO-2024-3281"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": " github.com/rancher/steve\u0027s users can issue watch commands for arbitrary resources"
}


Log in or create an account to share your comment.




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.