From 12623cf893578644f7b3e19de910c1962b1657ff Mon Sep 17 00:00:00 2001 From: "advisory-database[bot]" <45398580+advisory-database[bot]@users.noreply.github.com> Date: Fri, 11 Apr 2025 23:14:40 +0000 Subject: [PATCH] Publish Advisories GHSA-f5q9-j9r2-34gq GHSA-w9rv-xmf7-x3gh GHSA-9c5p-35gj-jqp4 GHSA-j5hq-5jcr-xwx7 GHSA-5qmp-9x47-92q8 GHSA-mq23-vvg7-xfm4 GHSA-8p83-cpfg-fj3g --- .../GHSA-f5q9-j9r2-34gq/GHSA-f5q9-j9r2-34gq.json | 1 + .../GHSA-w9rv-xmf7-x3gh/GHSA-w9rv-xmf7-x3gh.json | 2 +- .../GHSA-9c5p-35gj-jqp4/GHSA-9c5p-35gj-jqp4.json | 14 +++++++++++--- .../GHSA-j5hq-5jcr-xwx7/GHSA-j5hq-5jcr-xwx7.json | 14 +++++++++++--- .../GHSA-5qmp-9x47-92q8/GHSA-5qmp-9x47-92q8.json | 12 ++++++++++-- .../GHSA-mq23-vvg7-xfm4/GHSA-mq23-vvg7-xfm4.json | 12 ++++++++++-- .../GHSA-8p83-cpfg-fj3g/GHSA-8p83-cpfg-fj3g.json | 14 +++++++++++--- 7 files changed, 55 insertions(+), 14 deletions(-) diff --git a/advisories/github-reviewed/2022/12/GHSA-f5q9-j9r2-34gq/GHSA-f5q9-j9r2-34gq.json b/advisories/github-reviewed/2022/12/GHSA-f5q9-j9r2-34gq/GHSA-f5q9-j9r2-34gq.json index 35958e259aa..50f4d3580eb 100644 --- a/advisories/github-reviewed/2022/12/GHSA-f5q9-j9r2-34gq/GHSA-f5q9-j9r2-34gq.json +++ b/advisories/github-reviewed/2022/12/GHSA-f5q9-j9r2-34gq/GHSA-f5q9-j9r2-34gq.json @@ -51,6 +51,7 @@ ], "database_specific": { "cwe_ids": [ + "CWE-184", "CWE-77" ], "severity": "HIGH", diff --git a/advisories/github-reviewed/2022/12/GHSA-w9rv-xmf7-x3gh/GHSA-w9rv-xmf7-x3gh.json b/advisories/github-reviewed/2022/12/GHSA-w9rv-xmf7-x3gh/GHSA-w9rv-xmf7-x3gh.json index 9af6f02f636..2b9a72f51cf 100644 --- a/advisories/github-reviewed/2022/12/GHSA-w9rv-xmf7-x3gh/GHSA-w9rv-xmf7-x3gh.json +++ b/advisories/github-reviewed/2022/12/GHSA-w9rv-xmf7-x3gh/GHSA-w9rv-xmf7-x3gh.json @@ -1,7 +1,7 @@ { "schema_version": "1.4.0", "id": "GHSA-w9rv-xmf7-x3gh", - "modified": "2023-01-10T16:12:55Z", + "modified": "2025-04-11T23:13:52Z", "published": "2022-12-30T12:30:25Z", "aliases": [ "CVE-2022-44621" diff --git a/advisories/github-reviewed/2024/11/GHSA-9c5p-35gj-jqp4/GHSA-9c5p-35gj-jqp4.json b/advisories/github-reviewed/2024/11/GHSA-9c5p-35gj-jqp4/GHSA-9c5p-35gj-jqp4.json index 45980b3c293..a8f541e57aa 100644 --- a/advisories/github-reviewed/2024/11/GHSA-9c5p-35gj-jqp4/GHSA-9c5p-35gj-jqp4.json +++ b/advisories/github-reviewed/2024/11/GHSA-9c5p-35gj-jqp4/GHSA-9c5p-35gj-jqp4.json @@ -1,13 +1,13 @@ { "schema_version": "1.4.0", "id": "GHSA-9c5p-35gj-jqp4", - "modified": "2024-11-22T20:48:04Z", + "modified": "2025-04-11T23:13:19Z", "published": "2024-11-20T18:24:53Z", "aliases": [ "CVE-2024-52282" ], "summary": "Rancher Helm Applications may have sensitive values leaked", - "details": "### Impact\nA vulnerability has been identified within Rancher Manager whereby applications installed via Rancher Manager Apps Catalog store their Helm values directly into the `Apps` Custom Resource Definition, resulting in any users with `GET` access to it to be able to read any sensitive information that are contained within the Apps’ values. Additionally, the same information leaks into auditing logs when the audit level is set to equal or above 2.\n\nApplication charts without sensitive data are not affected by this vulnerability.\nThis vulnerability impacts any Helm applications installed on a Rancher Manager cluster, regardless of it being installed via the Marketplace or using the helm cli.\n\nPlease consult the associated [MITRE ATT&CK - Technique - Exploitation for Privilege Escalation](https://attack.mitre.org/techniques/T1068/) for further information about this category of attack.\n\n### Patches\nPatched versions include Rancher Manager `2.9.5` and `2.8.10`. The fix ensures that all Helm values for each App are stored as Kubernetes Secrets. After the upgrade, users are recommended to rotate passwords and secrets that may have been leaked while using the affected versions.\n\n### Workarounds\nNo workarounds are available, therefore users are advised to upgrade to a patched version of Rancher Manager.\nFor deployments that can’t be upgraded in a timely fashion, admins are advised to limit the impact by reducing the amount of users who can get or list the Apps’ CRD. Additionally, the same applies to the auditing logs if the Rancher Manager has audit logs enabled and set to level 2 or above.\n\n### For more information\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/).\n", + "details": "### Impact\nA vulnerability has been identified within Rancher Manager whereby applications installed via Rancher Manager Apps Catalog store their Helm values directly into the `Apps` Custom Resource Definition, resulting in any users with `GET` access to it to be able to read any sensitive information that are contained within the Apps’ values. Additionally, the same information leaks into auditing logs when the audit level is set to equal or above 2.\n\nApplication charts without sensitive data are not affected by this vulnerability.\nThis vulnerability impacts any Helm applications installed on a Rancher Manager cluster, regardless of it being installed via the Marketplace or using the helm cli.\n\nPlease consult the associated [MITRE ATT&CK - Technique - Exploitation for Privilege Escalation](https://attack.mitre.org/techniques/T1068/) for further information about this category of attack.\n\n### Patches\nPatched versions include Rancher Manager `2.9.5` and `2.8.10`. The fix ensures that all Helm values for each App are stored as Kubernetes Secrets. After the upgrade, users are recommended to rotate passwords and secrets that may have been leaked while using the affected versions.\n\n### Workarounds\nNo workarounds are available, therefore users are advised to upgrade to a patched version of Rancher Manager.\nFor deployments that can’t be upgraded in a timely fashion, admins are advised to limit the impact by reducing the amount of users who can get or list the Apps’ CRD. Additionally, the same applies to the auditing logs if the Rancher Manager has audit logs enabled and set to level 2 or above.\n\n### For more information\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/).", "severity": [ { "type": "CVSS_V3", @@ -59,6 +59,14 @@ "type": "WEB", "url": "https://github.com/rancher/rancher/security/advisories/GHSA-9c5p-35gj-jqp4" }, + { + "type": "ADVISORY", + "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-52282" + }, + { + "type": "WEB", + "url": "https://bugzilla.suse.com/show_bug.cgi?id=CVE-2024-52282" + }, { "type": "PACKAGE", "url": "https://github.com/rancher/rancher" @@ -75,6 +83,6 @@ "severity": "MODERATE", "github_reviewed": true, "github_reviewed_at": "2024-11-20T18:24:53Z", - "nvd_published_at": null + "nvd_published_at": "2025-04-11T11:15:41Z" } } \ No newline at end of file diff --git a/advisories/github-reviewed/2024/11/GHSA-j5hq-5jcr-xwx7/GHSA-j5hq-5jcr-xwx7.json b/advisories/github-reviewed/2024/11/GHSA-j5hq-5jcr-xwx7/GHSA-j5hq-5jcr-xwx7.json index 7f07cca07d5..6bb76bbf3c0 100644 --- a/advisories/github-reviewed/2024/11/GHSA-j5hq-5jcr-xwx7/GHSA-j5hq-5jcr-xwx7.json +++ b/advisories/github-reviewed/2024/11/GHSA-j5hq-5jcr-xwx7/GHSA-j5hq-5jcr-xwx7.json @@ -1,13 +1,13 @@ { "schema_version": "1.4.0", "id": "GHSA-j5hq-5jcr-xwx7", - "modified": "2024-11-22T20:47:39Z", + "modified": "2025-04-11T23:13:04Z", "published": "2024-11-20T18:23:25Z", "aliases": [ "CVE-2024-52280" ], "summary": " github.com/rancher/steve's users can issue watch commands for arbitrary resources", - "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's 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&CK - Technique - Valid Accounts](https://attack.mitre.org/techniques/T1078/003/) and [MITRE ATT&CK - 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'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.\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/).\n", + "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's 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&CK - Technique - Valid Accounts](https://attack.mitre.org/techniques/T1078/003/) and [MITRE ATT&CK - 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'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.\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/).", "severity": [ { "type": "CVSS_V3", @@ -40,10 +40,18 @@ "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" @@ -61,6 +69,6 @@ "severity": "HIGH", "github_reviewed": true, "github_reviewed_at": "2024-11-20T18:23:25Z", - "nvd_published_at": null + "nvd_published_at": "2025-04-11T12:15:14Z" } } \ No newline at end of file diff --git a/advisories/github-reviewed/2025/02/GHSA-5qmp-9x47-92q8/GHSA-5qmp-9x47-92q8.json b/advisories/github-reviewed/2025/02/GHSA-5qmp-9x47-92q8/GHSA-5qmp-9x47-92q8.json index 46d3c198cc7..d7c6865f27f 100644 --- a/advisories/github-reviewed/2025/02/GHSA-5qmp-9x47-92q8/GHSA-5qmp-9x47-92q8.json +++ b/advisories/github-reviewed/2025/02/GHSA-5qmp-9x47-92q8/GHSA-5qmp-9x47-92q8.json @@ -1,7 +1,7 @@ { "schema_version": "1.4.0", "id": "GHSA-5qmp-9x47-92q8", - "modified": "2025-02-27T18:27:41Z", + "modified": "2025-04-11T23:13:35Z", "published": "2025-02-27T18:27:41Z", "aliases": [ "CVE-2025-23387" @@ -78,6 +78,14 @@ "type": "WEB", "url": "https://github.com/rancher/rancher/security/advisories/GHSA-5qmp-9x47-92q8" }, + { + "type": "ADVISORY", + "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-23387" + }, + { + "type": "WEB", + "url": "https://bugzilla.suse.com/show_bug.cgi?id=CVE-2025-23387" + }, { "type": "PACKAGE", "url": "https://github.com/rancher/rancher" @@ -90,6 +98,6 @@ "severity": "MODERATE", "github_reviewed": true, "github_reviewed_at": "2025-02-27T18:27:41Z", - "nvd_published_at": null + "nvd_published_at": "2025-04-11T11:15:42Z" } } \ No newline at end of file diff --git a/advisories/github-reviewed/2025/02/GHSA-mq23-vvg7-xfm4/GHSA-mq23-vvg7-xfm4.json b/advisories/github-reviewed/2025/02/GHSA-mq23-vvg7-xfm4/GHSA-mq23-vvg7-xfm4.json index 737adc8f04a..0d2f6ebdd6b 100644 --- a/advisories/github-reviewed/2025/02/GHSA-mq23-vvg7-xfm4/GHSA-mq23-vvg7-xfm4.json +++ b/advisories/github-reviewed/2025/02/GHSA-mq23-vvg7-xfm4/GHSA-mq23-vvg7-xfm4.json @@ -1,7 +1,7 @@ { "schema_version": "1.4.0", "id": "GHSA-mq23-vvg7-xfm4", - "modified": "2025-03-13T15:15:31Z", + "modified": "2025-04-11T23:13:40Z", "published": "2025-02-27T18:27:56Z", "aliases": [ "CVE-2025-23389" @@ -78,6 +78,14 @@ "type": "WEB", "url": "https://github.com/rancher/rancher/security/advisories/GHSA-mq23-vvg7-xfm4" }, + { + "type": "ADVISORY", + "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-23389" + }, + { + "type": "WEB", + "url": "https://bugzilla.suse.com/show_bug.cgi?id=CVE-2025-23389" + }, { "type": "PACKAGE", "url": "https://github.com/rancher/rancher" @@ -95,6 +103,6 @@ "severity": "HIGH", "github_reviewed": true, "github_reviewed_at": "2025-02-27T18:27:56Z", - "nvd_published_at": null + "nvd_published_at": "2025-04-11T11:15:42Z" } } \ No newline at end of file diff --git a/advisories/github-reviewed/2025/04/GHSA-8p83-cpfg-fj3g/GHSA-8p83-cpfg-fj3g.json b/advisories/github-reviewed/2025/04/GHSA-8p83-cpfg-fj3g/GHSA-8p83-cpfg-fj3g.json index 4f7024b2166..bf8c0f93ed3 100644 --- a/advisories/github-reviewed/2025/04/GHSA-8p83-cpfg-fj3g/GHSA-8p83-cpfg-fj3g.json +++ b/advisories/github-reviewed/2025/04/GHSA-8p83-cpfg-fj3g/GHSA-8p83-cpfg-fj3g.json @@ -1,13 +1,13 @@ { "schema_version": "1.4.0", "id": "GHSA-8p83-cpfg-fj3g", - "modified": "2025-04-01T14:19:30Z", + "modified": "2025-04-11T23:13:29Z", "published": "2025-04-01T14:19:30Z", "aliases": [ "CVE-2025-23391" ], "summary": "Rancher: Restricted Administrator can change Administrator's passwords", - "details": "### Impact\nA vulnerability has been identified within Rancher where a Restricted Administrator can change the password of Administrators and take over their accounts. \n\nA Restricted Administrator should be not allowed to change the password of more privileged users unless it contains the Manage Users permissions.\n\nRancher deployments where the Restricted Administrator role is not being used are not affected by this CVE.\nPlease consult the associated [MITRE ATT&CK - Technique - Abuse Elevation Control Mechanism](https://attack.mitre.org/techniques/T1548/) for further information about this category of attack.\n\n### Patches\nThe fix introduces a few changes:\n1. If the user has a manage-users verb, the user is allowed to edit/delete users. That way the Manage Users built in role will still be able to edit ALL users.\n2. If the user doesn't have manage-users, just edit or delete, then there is a check to ensure that the User being edited only has rules equal to or less than the editor.\n\nPatched versions include releases `v2.8.14`, `v2.9.8`, `v2.10.4` and `v2.11.0`\n\n### Workarounds\nUsers are recommended to upgrade, as soon as possible, to a version of Rancher Manager that contains the fix.\nIf users can't upgrade, the following are recommended:\n1. Limit access to Rancher Restricted Admin only to trusted users.\n2. Downgrade Restricted Administrators to custom roles with limited permissions.\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/).", + "details": "### Impact\nA vulnerability has been identified within Rancher where a Restricted Administrator can change the password of Administrators and take over their accounts. \n\nA Restricted Administrator should be not allowed to change the password of more privileged users unless it contains the Manage Users permissions.\n\nRancher deployments where the Restricted Administrator role is not being used are not affected by this CVE.\nPlease consult the associated [MITRE ATT&CK - Technique - Abuse Elevation Control Mechanism](https://attack.mitre.org/techniques/T1548/) for further information about this category of attack.\n\n### Patches\nThe fix introduces a few changes:\n1. If the user has a manage-users verb, the user is allowed to edit/delete users. That way the Manage Users built in role will still be able to edit ALL users.\n2. If the user doesn't have manage-users, just edit or delete, then there is a check to ensure that the User being edited only has rules equal to or less than the editor.\n\nPatched versions include releases `v2.8.14`, `v2.9.8`, `v2.10.4` and `v2.11.0`\n\n### Workarounds\nUsers are recommended to upgrade, as soon as possible, to a version of Rancher Manager that contains the fix.\nIf users can't upgrade, the following are recommended:\n1. Limit access to Rancher Restricted Admin only to trusted users.\n2. Downgrade Restricted Administrators to custom roles with limited permissions.\n\n### Credits\nThis issue was identified and reported by Xavier Duthil from OVHcloud.\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/).", "severity": [ { "type": "CVSS_V3", @@ -78,6 +78,14 @@ "type": "WEB", "url": "https://github.com/rancher/rancher/security/advisories/GHSA-8p83-cpfg-fj3g" }, + { + "type": "ADVISORY", + "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-23391" + }, + { + "type": "WEB", + "url": "https://bugzilla.suse.com/show_bug.cgi?id=CVE-2025-23391" + }, { "type": "PACKAGE", "url": "https://github.com/rancher/rancher" @@ -90,6 +98,6 @@ "severity": "CRITICAL", "github_reviewed": true, "github_reviewed_at": "2025-04-01T14:19:30Z", - "nvd_published_at": null + "nvd_published_at": "2025-04-11T11:15:42Z" } } \ No newline at end of file