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
http://packetstormsecurity.com/files/159794/GitHub-Widespread-Injection.html
https://github.com/actions/toolkit/security/advisories/GHSA-mfwh-5m23-j46w
Related Vulnerabilities
CVE-2021-43306 Vulnerability in maven package org.webjars.bower:jquery-validation
CVE-2021-33041 Vulnerability in npm package vmd
CVE-2023-26487 Vulnerability in npm package vega-functions
CVE-2021-31405 Vulnerability in maven package com.vaadin:vaadin-text-field-flow
CVE-2022-36033 Vulnerability in maven package org.jsoup:jsoup