CVE-2020-15228 Environment Variable Injection in GitHub Actions
- Published
- Updated
- Exploit status
- Public exploit available
Description
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.
Upgrade path
3 packages: 2 fixed.
| Package | Affected | Fixed in | Status |
|---|---|---|---|
| actions @actions/core(npm) | < 1.2.6 | 1.2.6 | Fixed |
| toolkit project toolkit | < 1.2.6 | 1.2.6 | Fixed |
| actions toolkit | = < 1.2.6 | No fix listed | Versions listed |
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| actions @actions/core(npm) | < 1.2.6 | 1.2.6 |
| toolkit project toolkit | < 1.2.6 | 1.2.6 |
| actions toolkit | = < 1.2.6 | No fix listed |
References
- github.com third-party-advisory vendor-advisory
- nvd.nist.gov third-party-advisory vendor-advisory
- packetstormsecurity.com exploit third-party-advisory vdb-entry
- github.com
- github.com