Skip to content

Commit c8b046c

Browse files
1 parent 59edd4d commit c8b046c

File tree

4 files changed

+323
-5
lines changed

4 files changed

+323
-5
lines changed
Lines changed: 65 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,65 @@
1+
{
2+
"schema_version": "1.4.0",
3+
"id": "GHSA-5xq9-5g24-4g6f",
4+
"modified": "2025-09-26T13:01:10Z",
5+
"published": "2025-09-26T13:01:10Z",
6+
"aliases": [
7+
"CVE-2025-59844"
8+
],
9+
"summary": "Argument injection vulnerability in SonarQube Scan Action",
10+
"details": "A command injection vulnerability exists in SonarQube GitHub Action prior to v6.0.0 when workflows pass user-controlled input to the args parameter on Windows runners without proper validation. This vulnerability bypasses a previous security fix and allows arbitrary command execution, potentially leading to exposure of sensitive environment variables and compromise of the runner environment.\n\n\n### Patches\nThe vulnerability has been fixed in version v6.0.0. Users should upgrade to this version or later.\n\n\n### References\n- Community Post: https://community.sonarsource.com/t/sonarqube-scanner-github-action-v6/149281 \n- Fix release: https://github.com/SonarSource/sonarqube-scan-action/releases/tag/v6.0.0",
11+
"severity": [
12+
{
13+
"type": "CVSS_V4",
14+
"score": "CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N"
15+
}
16+
],
17+
"affected": [
18+
{
19+
"package": {
20+
"ecosystem": "GitHub Actions",
21+
"name": "SonarSource/sonarqube-scan-action"
22+
},
23+
"ranges": [
24+
{
25+
"type": "ECOSYSTEM",
26+
"events": [
27+
{
28+
"introduced": "4.0.0"
29+
},
30+
{
31+
"fixed": "6.0.0"
32+
}
33+
]
34+
}
35+
]
36+
}
37+
],
38+
"references": [
39+
{
40+
"type": "WEB",
41+
"url": "https://github.com/SonarSource/sonarqube-scan-action/security/advisories/GHSA-5xq9-5g24-4g6f"
42+
},
43+
{
44+
"type": "WEB",
45+
"url": "https://community.sonarsource.com/t/sonarqube-scanner-github-action-v6/149281"
46+
},
47+
{
48+
"type": "PACKAGE",
49+
"url": "https://github.com/SonarSource/sonarqube-scan-action"
50+
},
51+
{
52+
"type": "WEB",
53+
"url": "https://github.com/SonarSource/sonarqube-scan-action/releases/tag/v6.0.0"
54+
}
55+
],
56+
"database_specific": {
57+
"cwe_ids": [
58+
"CWE-78"
59+
],
60+
"severity": "HIGH",
61+
"github_reviewed": true,
62+
"github_reviewed_at": "2025-09-26T13:01:10Z",
63+
"nvd_published_at": null
64+
}
65+
}

advisories/unreviewed/2025/09/GHSA-9x36-c74v-fgr6/GHSA-9x36-c74v-fgr6.json renamed to advisories/github-reviewed/2025/09/GHSA-9x36-c74v-fgr6/GHSA-9x36-c74v-fgr6.json

Lines changed: 30 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,12 @@
11
{
22
"schema_version": "1.4.0",
33
"id": "GHSA-9x36-c74v-fgr6",
4-
"modified": "2025-09-25T18:30:33Z",
4+
"modified": "2025-09-26T13:01:32Z",
55
"published": "2025-09-25T18:30:33Z",
66
"aliases": [
77
"CVE-2025-10952"
88
],
9+
"summary": "ml-logger file handler allows reading arbitrary files",
910
"details": "A security flaw has been discovered in geyang ml-logger up to acf255bade5be6ad88d90735c8367b28cbe3a743. Affected by this issue is the function stream_handler of the file ml_logger/server.py of the component File Handler. Performing manipulation of the argument key results in information disclosure. The attack can be initiated remotely. The exploit has been released to the public and may be exploited. Continious delivery with rolling releases is used by this product. Therefore, no version details of affected nor updated releases are available.",
1011
"severity": [
1112
{
@@ -14,10 +15,30 @@
1415
},
1516
{
1617
"type": "CVSS_V4",
17-
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X"
18+
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P"
19+
}
20+
],
21+
"affected": [
22+
{
23+
"package": {
24+
"ecosystem": "PyPI",
25+
"name": "ml-logger"
26+
},
27+
"ranges": [
28+
{
29+
"type": "ECOSYSTEM",
30+
"events": [
31+
{
32+
"introduced": "0"
33+
},
34+
{
35+
"last_affected": "0.10.36"
36+
}
37+
]
38+
}
39+
]
1840
}
1941
],
20-
"affected": [],
2142
"references": [
2243
{
2344
"type": "ADVISORY",
@@ -27,6 +48,10 @@
2748
"type": "WEB",
2849
"url": "https://github.com/geyang/ml-logger/issues/74"
2950
},
51+
{
52+
"type": "PACKAGE",
53+
"url": "https://github.com/geyang/ml-logger"
54+
},
3055
{
3156
"type": "WEB",
3257
"url": "https://vuldb.com/?ctiid.325822"
@@ -45,8 +70,8 @@
4570
"CWE-200"
4671
],
4772
"severity": "MODERATE",
48-
"github_reviewed": false,
49-
"github_reviewed_at": null,
73+
"github_reviewed": true,
74+
"github_reviewed_at": "2025-09-26T13:01:32Z",
5075
"nvd_published_at": "2025-09-25T16:15:31Z"
5176
}
5277
}
Lines changed: 114 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,114 @@
1+
{
2+
"schema_version": "1.4.0",
3+
"id": "GHSA-mjcp-rj3c-36fr",
4+
"modified": "2025-09-26T13:02:38Z",
5+
"published": "2025-09-26T13:02:38Z",
6+
"aliases": [
7+
"CVE-2025-54468"
8+
],
9+
"summary": "Rancher sends sensitive information to external services through the `/meta/proxy` endpoint",
10+
"details": "### Impact\n\nA vulnerability has been identified within Rancher Manager whereby `Impersonate-Extra-*` headers are being sent to an external entity, for example `amazonaws.com`, via the `/meta/proxy` Rancher endpoint. These headers may contain identifiable and/or sensitive information e.g. email addresses.\n\nIf the authentication provider is configured to have email or other sensitive and/or identifiable information as part of the username and principal ID then when a new cloud credential is being created in Rancher Manager this information is sent to an external entity such as `amazonaws.com`, in case of an AWS cloud credentials, in `Impersonate-Extra-Username` and/or `Impersonate-Extra-Principalid` headers. Please note that neither password, password hashes or Rancher’s related authentication tokens are leaked in those requests.\n\nThe entities to which such information is sent to are limited by the whitelisted domains specified in `nodedrivers.management.cattle.io` objects. \n\nFor example, the Amazon EC2 node driver contains the following whitelisted domains:\n\n- `iam.amazonaws.com`\n- `iam.us-gov.amazonaws.com`\n- `iam.%.amazonaws.com.cn`\n- `iam.global.api.aws`\n- `ec2.%.amazonaws.com`\n- `ec2.%.amazonaws.com.cn`\n- `ec2.%.api.aws`\n- `eks.%.amazonaws.com`\n- `eks.%.amazonaws.com.cn`\n- `eks.%.api.aws`\n- `kms.%.amazonaws.com`\n- `kms.%.amazonaws.com.cn`\n- `kms.%.api.aws`\n\nWhile the DigitalOcean driver contains the following whitelisted domain:\n\n- `api.digitalocean.com`\n\n### Patches\n\nThis vulnerability is addressed by filtering all `Impersonate-*` headers from the original request by the `/meta/proxy` endpoint.\n\nPatched versions of Rancher include releases v2.12.2, v2.11.6, v2.10.10, and v2.9.12. \n\n### Workarounds\n\nThere are no known workarounds for this issue.\n\n### References\n\nIf you have any questions or comments about this advisory:\n\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/).",
11+
"severity": [
12+
{
13+
"type": "CVSS_V3",
14+
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:N/A:N"
15+
}
16+
],
17+
"affected": [
18+
{
19+
"package": {
20+
"ecosystem": "Go",
21+
"name": "github.com/rancher/rancher"
22+
},
23+
"ranges": [
24+
{
25+
"type": "ECOSYSTEM",
26+
"events": [
27+
{
28+
"introduced": "2.12.0"
29+
},
30+
{
31+
"fixed": "2.12.2"
32+
}
33+
]
34+
}
35+
]
36+
},
37+
{
38+
"package": {
39+
"ecosystem": "Go",
40+
"name": "github.com/rancher/rancher"
41+
},
42+
"ranges": [
43+
{
44+
"type": "ECOSYSTEM",
45+
"events": [
46+
{
47+
"introduced": "2.11.0"
48+
},
49+
{
50+
"fixed": "2.11.6"
51+
}
52+
]
53+
}
54+
]
55+
},
56+
{
57+
"package": {
58+
"ecosystem": "Go",
59+
"name": "github.com/rancher/rancher"
60+
},
61+
"ranges": [
62+
{
63+
"type": "ECOSYSTEM",
64+
"events": [
65+
{
66+
"introduced": "2.10.0"
67+
},
68+
{
69+
"fixed": "2.10.10"
70+
}
71+
]
72+
}
73+
]
74+
},
75+
{
76+
"package": {
77+
"ecosystem": "Go",
78+
"name": "github.com/rancher/rancher"
79+
},
80+
"ranges": [
81+
{
82+
"type": "ECOSYSTEM",
83+
"events": [
84+
{
85+
"introduced": "2.9.0"
86+
},
87+
{
88+
"fixed": "2.9.12"
89+
}
90+
]
91+
}
92+
]
93+
}
94+
],
95+
"references": [
96+
{
97+
"type": "WEB",
98+
"url": "https://github.com/rancher/rancher/security/advisories/GHSA-mjcp-rj3c-36fr"
99+
},
100+
{
101+
"type": "PACKAGE",
102+
"url": "https://github.com/rancher/rancher"
103+
}
104+
],
105+
"database_specific": {
106+
"cwe_ids": [
107+
"CWE-200"
108+
],
109+
"severity": "MODERATE",
110+
"github_reviewed": true,
111+
"github_reviewed_at": "2025-09-26T13:02:38Z",
112+
"nvd_published_at": null
113+
}
114+
}
Lines changed: 114 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,114 @@
1+
{
2+
"schema_version": "1.4.0",
3+
"id": "GHSA-v3vj-5868-2ch2",
4+
"modified": "2025-09-26T13:02:44Z",
5+
"published": "2025-09-26T13:02:44Z",
6+
"aliases": [
7+
"CVE-2024-58267"
8+
],
9+
"summary": "Rancher CLI SAML authentication is vulnerable to phishing attacks",
10+
"details": "### Impact\n\nA vulnerability has been identified within Rancher Manager whereby the SAML authentication from the Rancher CLI tool is vulnerable to phishing attacks. The custom authentication protocol for SAML-based providers can be abused to steal Rancher’s authentication tokens.\n\nRancher Manager deployments without SAML authentication enabled are not affected by this vulnerability.\n\nAn attacker can generate a phishing SAML login URL which contains a `publicKey` and `requestId` controlled by the attacker. The attacker can then give the link to another user (eg: admin) and if the victim goes to the link unsuspectingly, they might not notice the bad parameters in the URL. The user will be prompted to login and might believe that its session has ended so they need to re-login. By clicking on the link, they will be logged in and an encrypted token will be created with the attacker's public key. The attacker can then decrypt the victim’s Rancher token, enabling the attack\n\nPlease consult the associated [MITRE ATTACK Techniques - Privilege Escalation](https://attack.mitre.org/tactics/TA0004/) for further information about this category of attack.\n\n### Patches\n\nThis vulnerability is addressed by changes in both Rancher Manager and the CLI. The fixed versions:\n\n1. The Rancher CLI now reports the `requestId` that is relevant to the authentication session in process as a separate message to the terminal, making it easier for the user to identify and compare.\n2. The Rancher login page for SAML authentication will display a suitable warning to ensure that the user seeing the login page is aware of the login process with the related `requestId`, enabling users to verify whether the request was intended or not.\n\nPatched versions of Rancher include releases v2.12.2, v2.11.6, v2.10.10, and v2.9.12.\n\n### Workarounds\n\nIf you cannot update to one of the fixed versions, make sure to check the URL printed by the Rancher CLI when performing a SAML authentication flow, especially the `requestId` parameter. The URL and the `requestId` printed by the CLI must be the same URL that you access and see when finalizing the SAML authentication flow in your browser for the Rancher UI. The URL has the format:\n\n- `<rancher_ui_address>/dashboard/auth/login?requestId=<requestid>&publicKey=<pubkey>&responseType=<responsetype>` \n\nIf the URL presented in the browser is different from the one logged by the CLI, the user must not proceed with the login, as they might be under a phishing attack.\n\n### References\n\nIf you have any questions or comments about this advisory:\n\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/).",
11+
"severity": [
12+
{
13+
"type": "CVSS_V3",
14+
"score": "CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H"
15+
}
16+
],
17+
"affected": [
18+
{
19+
"package": {
20+
"ecosystem": "Go",
21+
"name": "github.com/rancher/rancher"
22+
},
23+
"ranges": [
24+
{
25+
"type": "ECOSYSTEM",
26+
"events": [
27+
{
28+
"introduced": "2.12.0"
29+
},
30+
{
31+
"fixed": "2.12.2"
32+
}
33+
]
34+
}
35+
]
36+
},
37+
{
38+
"package": {
39+
"ecosystem": "Go",
40+
"name": "github.com/rancher/rancher"
41+
},
42+
"ranges": [
43+
{
44+
"type": "ECOSYSTEM",
45+
"events": [
46+
{
47+
"introduced": "2.11.0"
48+
},
49+
{
50+
"fixed": "2.11.6"
51+
}
52+
]
53+
}
54+
]
55+
},
56+
{
57+
"package": {
58+
"ecosystem": "Go",
59+
"name": "github.com/rancher/rancher"
60+
},
61+
"ranges": [
62+
{
63+
"type": "ECOSYSTEM",
64+
"events": [
65+
{
66+
"introduced": "2.10.0"
67+
},
68+
{
69+
"fixed": "2.10.10"
70+
}
71+
]
72+
}
73+
]
74+
},
75+
{
76+
"package": {
77+
"ecosystem": "Go",
78+
"name": "github.com/rancher/rancher"
79+
},
80+
"ranges": [
81+
{
82+
"type": "ECOSYSTEM",
83+
"events": [
84+
{
85+
"introduced": "2.9.0"
86+
},
87+
{
88+
"fixed": "2.9.12"
89+
}
90+
]
91+
}
92+
]
93+
}
94+
],
95+
"references": [
96+
{
97+
"type": "WEB",
98+
"url": "https://github.com/rancher/rancher/security/advisories/GHSA-v3vj-5868-2ch2"
99+
},
100+
{
101+
"type": "PACKAGE",
102+
"url": "https://github.com/rancher/rancher"
103+
}
104+
],
105+
"database_specific": {
106+
"cwe_ids": [
107+
"CWE-345"
108+
],
109+
"severity": "HIGH",
110+
"github_reviewed": true,
111+
"github_reviewed_at": "2025-09-26T13:02:44Z",
112+
"nvd_published_at": null
113+
}
114+
}

0 commit comments

Comments
 (0)