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.
Remediation
References
https://github.com/actions/toolkit/security/advisories/GHSA-mfwh-5m23-j46w
http://packetstormsecurity.com/files/159794/GitHub-Widespread-Injection.html
Related Vulnerabilities
CVE-2023-46604 Vulnerability in maven package org.apache.activemq:activemq-client
CVE-2021-27644 Vulnerability in maven package org.apache.dolphinscheduler:dolphinscheduler-server
CVE-2021-30246 Vulnerability in maven package org.webjars.bower:jsrsasign
CVE-2022-29078 Vulnerability in maven package org.webjars.npm:ejs
CVE-2017-1000048 Vulnerability in maven package org.webjars.bower:qs