CVE-2020-15228
Environment Variable Injection in GitHub Actions
In the `@actions/core` npm module before version 1.2.6,`addPath` and `exportVariable` functions communicate with the Actions Runner over stdout by generating a string in a specific format. Workflows that log untrusted data to stdout may invoke these commands, resulting in the path or environment variables being modified without the intention of the workflow or action author. The runner will release an update that disables the `set-env` and `add-path` workflow commands in the near future. For now, users should upgrade to `@actions/core v1.2.6` or later, and replace any instance of the `set-env` or `add-path` commands in their workflows with the new Environment File Syntax. Workflows and actions using the old commands or older versions of the toolkit will start to warn, then error out during workflow execution.
- Affected
- actions · toolkit
- CVSS v3.1 NVD
- 5.0 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:N - CVSS v3.1 GITHUB
- 3.5 LOW
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:N/A:N - CVSS v2.0 NVD
- 4.0 MEDIUM
AV:N/AC:L/Au:S/C:N/I:P/A:N - EPSS
- 1.49% chance of exploitation in the next 30 days, 74th percentile
- Published
- 2020-10-01
- Updated
- 2024-08-04