From a1f178cf66da28765c529d7f9396f50759742b7d Mon Sep 17 00:00:00 2001 From: "advisory-database[bot]" <45398580+advisory-database[bot]@users.noreply.github.com> Date: Wed, 2 Apr 2025 22:38:36 +0000 Subject: [PATCH] Publish Advisories GHSA-26wh-cc3r-w6pj GHSA-c9pr-q8gx-3mgp --- .../GHSA-26wh-cc3r-w6pj.json | 65 +++++++++++++++ .../GHSA-c9pr-q8gx-3mgp.json | 80 +++++++++++++++++++ 2 files changed, 145 insertions(+) create mode 100644 advisories/github-reviewed/2025/04/GHSA-26wh-cc3r-w6pj/GHSA-26wh-cc3r-w6pj.json create mode 100644 advisories/github-reviewed/2025/04/GHSA-c9pr-q8gx-3mgp/GHSA-c9pr-q8gx-3mgp.json diff --git a/advisories/github-reviewed/2025/04/GHSA-26wh-cc3r-w6pj/GHSA-26wh-cc3r-w6pj.json b/advisories/github-reviewed/2025/04/GHSA-26wh-cc3r-w6pj/GHSA-26wh-cc3r-w6pj.json new file mode 100644 index 00000000000..f0ebd9e455a --- /dev/null +++ b/advisories/github-reviewed/2025/04/GHSA-26wh-cc3r-w6pj/GHSA-26wh-cc3r-w6pj.json @@ -0,0 +1,65 @@ +{ + "schema_version": "1.4.0", + "id": "GHSA-26wh-cc3r-w6pj", + "modified": "2025-04-02T22:36:03Z", + "published": "2025-04-02T22:36:03Z", + "aliases": [ + "CVE-2025-31479" + ], + "summary": "canonical/get-workflow-version-action can leak a partial GITHUB_TOKEN in exception output", + "details": "### Impact\nUsers using the [`github-token` input](https://github.com/canonical/get-workflow-version-action/blob/a5d53b08d254a157ea441c9819ea5002ffc12edc/action.yaml#L10) are impacted.\n\nIf the `get-workflow-version-action` step fails, the exception output may include the GITHUB_TOKEN. If the full token is included in the exception output, GitHub will automatically redact the secret from the GitHub Actions logs. However, the token may be truncated—causing part of the GITHUB_TOKEN to be displayed in plaintext in the GitHub Actions logs.\n\nAnyone with read access to the GitHub repository can view GitHub Actions logs. For public repositories, anyone can view the GitHub Actions logs.\n\nThe opportunity to exploit this vulnerability is limited—the GITHUB_TOKEN is automatically revoked when the job completes. However, there is an opportunity for an attack in the time between the GITHUB_TOKEN being displayed in the logs and the completion of the job. Normally this is less than a second, but it may be greater if [`continue-on-error`](https://docs.github.com/en/actions/writing-workflows/workflow-syntax-for-github-actions#jobsjob_idstepscontinue-on-error) is used in the `get-workflow-version-action` step or if [status check functions](https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/evaluate-expressions-in-workflows-and-actions#status-check-functions) are used in a later step in the same job. For an example of an attack in the time between the GITHUB_TOKEN being displayed in the logs & the completion of the job, see https://www.praetorian.com/blog/codeqleaked-public-secrets-exposure-leads-to-supply-chain-attack-on-github-codeql/\n\nFor users who passed the GITHUB_TOKEN to the `github-token` input, update to `v1.0.1`. Any secrets that were partially leaked while using `v1.0.0` should have already been revoked, since the GITHUB_TOKEN is automatically revoked when the job completes. However, in the unlikely event that an attack was executed using a GITHUB_TOKEN before it was revoked (as described above), users' repositories may still be impacted—for example, a sophisticated attack could have used the GITHUB_TOKEN to push something to the repository.\n\nThe potential effects of an attack depend on the permissions of any GITHUB_TOKENs that were leaked. However, in a very sophisticated attack, even a GITHUB_TOKEN with read-only permissions can affect other GitHub Actions in the same repository if those actions use the Actions [cache](https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/caching-dependencies-to-speed-up-workflows). For more information, see the \"But Wait, There’s More\" section of https://www.praetorian.com/blog/codeqleaked-public-secrets-exposure-leads-to-supply-chain-attack-on-github-codeql/ and https://github.com/AdnaneKhan/Cacheract\n\nIf any users used a long-lived secret (e.g. a personal access token) instead of the GITHUB_TOKEN in the `github-token` input, they should immediately revoke that secret. The `get-workflow-version-action`'s documentation & examples all instructed the user to use the GITHUB_TOKEN, so it is unlikely that users used a long-lived secret instead of the GITHUB_TOKEN.\n\n### Patches\nThis has been fixed in `v1.0.1`. Also, the `v1` tag has been updated to include the fix.\n\n### References\nhttps://github.com/canonical/get-workflow-version-action/issues/2", + "severity": [ + { + "type": "CVSS_V3", + "score": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:H/A:H" + } + ], + "affected": [ + { + "package": { + "ecosystem": "GitHub Actions", + "name": "canonical/get-workflow-version-action" + }, + "ranges": [ + { + "type": "ECOSYSTEM", + "events": [ + { + "introduced": "0" + }, + { + "fixed": "1.0.1" + } + ] + } + ] + } + ], + "references": [ + { + "type": "WEB", + "url": "https://github.com/canonical/get-workflow-version-action/security/advisories/GHSA-26wh-cc3r-w6pj" + }, + { + "type": "WEB", + "url": "https://github.com/canonical/get-workflow-version-action/issues/2" + }, + { + "type": "WEB", + "url": "https://github.com/canonical/get-workflow-version-action/commit/88281a62e96e1c0ef4df30352ae0668a9f3e3369" + }, + { + "type": "PACKAGE", + "url": "https://github.com/canonical/get-workflow-version-action" + } + ], + "database_specific": { + "cwe_ids": [ + "CWE-532" + ], + "severity": "HIGH", + "github_reviewed": true, + "github_reviewed_at": "2025-04-02T22:36:03Z", + "nvd_published_at": null + } +} \ No newline at end of file diff --git a/advisories/github-reviewed/2025/04/GHSA-c9pr-q8gx-3mgp/GHSA-c9pr-q8gx-3mgp.json b/advisories/github-reviewed/2025/04/GHSA-c9pr-q8gx-3mgp/GHSA-c9pr-q8gx-3mgp.json new file mode 100644 index 00000000000..d59aed55dd6 --- /dev/null +++ b/advisories/github-reviewed/2025/04/GHSA-c9pr-q8gx-3mgp/GHSA-c9pr-q8gx-3mgp.json @@ -0,0 +1,80 @@ +{ + "schema_version": "1.4.0", + "id": "GHSA-c9pr-q8gx-3mgp", + "modified": "2025-04-02T22:36:45Z", + "published": "2025-04-02T22:36:45Z", + "aliases": [ + "CVE-2025-31477" + ], + "summary": "Improper Scope Validation in the `open` Endpoint of `tauri-plugin-shell`", + "details": "### Impact\n\nThe Tauri [`shell`](https://tauri.app/plugin/shell/) plugin exposes functionality to execute code and open programs on the system. The [`open`](https://tauri.app/reference/javascript/shell/#open) endpoint of this plugin is designed to allow open functionality with the system opener (e.g. \n `xdg-open` on Linux). This was meant to be restricted to a reasonable number of protocols like `https` or `mailto` by default.\n\nThis default restriction was not functional due to improper validation of the allowed protocols, allowing for potentially dangerous protocols like `file://`, `smb://`, or `nfs://` and others to be opened by the system registered protocol handler.\n\nBy passing untrusted user input to the `open` endpoint these potentially dangerous protocols can be abused to gain remote code execution on the system. This either requires direct exposure of the endpoint to application users or code execution in the frontend of a Tauri application.\n\nYou are not affected if you have explicitly configured a validation regex or manually set the `open` endpoint to `true` in the plugin configuration. \n\nTechnically the scope was never a limitation for the rust side as it is not seen as an enforceable security boundary but we decided to mark the rust crate as affected since the plugin does not need to be a frontend dependency to be exposed.\n\n### Patches\n\nThe issue has been patched in the `2.2.1` version of the plugin.\nThe plugin now differentiates between an unset scope and an explicit validation disable for the `open` endpoint.\n\n### Workarounds \n\nA way to prevent arbitrary protocols would be setting the shell plugin configuration value `open` to `true`.\n\n`tauri.conf.json`\n```json5 \n\"plugins\": {\n \"shell\": {\n \"open\": true\n },\n}\n```\n\nThe above will only allow `mailto`, `http` and `https` links to be opened.\n\nIf the `open` endpoint should not be allowed at all there are two possible workarounds.\n- Defining a non matching regex like `tauri^` in the plugin configuration\n- Removing `shell:default` and all instances of `shell:allow-open` from the [`capabilities`](https://tauri.app/security/capabilities/) \n\nAlternatively we recommend usage of the [`opener`](https://tauri.app/plugin/opener/) plugin, as the shell plugin deprecated the `open` endpoint previously.\n### References\n\n#### PoC\n\nThis is a windows specific proof of concept.\n\n1. Use `create-tauri-app` to make a new Tauri app.\n2. Run `tauri add shell` to add the shell plugin.\n3. Execute `await window.__TAURI_INTERNALS__.invoke(\"plugin:shell|open\", {path: \"file:///c:/windows/system32/calc.exe\"});` in the developer console.\n4. Observe the calculator being executed", + "severity": [ + { + "type": "CVSS_V4", + "score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N" + } + ], + "affected": [ + { + "package": { + "ecosystem": "crates.io", + "name": "tauri-plugin-shell" + }, + "ranges": [ + { + "type": "ECOSYSTEM", + "events": [ + { + "introduced": "0" + }, + { + "fixed": "2.2.1" + } + ] + } + ] + }, + { + "package": { + "ecosystem": "npm", + "name": "@tauri-apps/plugin-shell" + }, + "ranges": [ + { + "type": "ECOSYSTEM", + "events": [ + { + "introduced": "0" + }, + { + "fixed": "2.2.1" + } + ] + } + ] + } + ], + "references": [ + { + "type": "WEB", + "url": "https://github.com/tauri-apps/plugins-workspace/security/advisories/GHSA-c9pr-q8gx-3mgp" + }, + { + "type": "WEB", + "url": "https://github.com/tauri-apps/plugins-workspace/commit/9cf0390a52497e273db1a1b613a0e26827aa327c" + }, + { + "type": "PACKAGE", + "url": "https://github.com/tauri-apps/plugins-workspace" + } + ], + "database_specific": { + "cwe_ids": [ + "CWE-20" + ], + "severity": "CRITICAL", + "github_reviewed": true, + "github_reviewed_at": "2025-04-02T22:36:45Z", + "nvd_published_at": null + } +} \ No newline at end of file