CVE-2023-30623 – embano1/wip

Package

Manager: github_actions
Name: embano1/wip
Vulnerable Version: >=0 <2

Severity

Level: High

CVSS v3.1: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

CVSS v4.0: 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

EPSS: 0.01343 pctl0.79274

Details

Arbitrary command injection in embano1/wip ## Summary The `embano1/wip` action uses the `github.event.pull_request.title` parameter in an insecure way. The title parameter is used in a run statement - resulting in a command injection vulnerability due to string interpolation. ## Details and Impact This vulnerability can be triggered by any user on GitHub. They just need to create a pull request with a commit message containing an exploit. (Note that first-time PR requests will not be run - but the attacker can submit a valid PR before submitting an invalid PR). The commit can be genuine, but the commit message can be malicious. This can be used to execute code on the GitHub runners (potentially use it for crypto-mining, and waste your resources) and can be used to exfiltrate any secrets that you use in the CI pipeline (including repository tokens). [Here](https://securitylab.github.com/research/github-actions-untrusted-input/) is a set of blog posts by Github's security team explaining this issue. ## How to update existing workflows Replace the following line in your workflow using this action with the `v2` branch name or commit pointing to this branch: ```yaml uses: embano1/wip@v2 ``` Or using the exact commit: ```yaml uses: embano1/wip@c25450f77ed02c20d00b76ee3b33ff43838739a2 # v2 ```

Metadata

Created: 2023-04-24T22:32:32Z
Modified: 2023-04-25T16:34:43Z
Source: https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2023/04/GHSA-rg3q-prf8-qxmp/GHSA-rg3q-prf8-qxmp.json
CWE IDs: ["CWE-77"]
Alternative ID: GHSA-rg3q-prf8-qxmp
Finding: F422
Auto approve: 1