chore(deps): update dependency @actions/core to v1.9.1 [security] #32
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.2.4->1.9.1GitHub Vulnerability Alerts
CVE-2020-15228
Impact
The
@actions/corenpm moduleaddPathandexportVariablefunctions 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.Patches
The runner will release an update that disables the
set-envandadd-pathworkflow commands in the near future. For now, users should upgrade to@actions/core v1.2.6or later, and replace any instance of theset-envoradd-pathcommands 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.Workarounds
None, it is strongly suggested that you upgrade as soon as possible.
For more information
If you have any questions or comments about this advisory:
CVE-2022-35954
Impact
The
core.exportVariablefunction uses a well known delimiter that attackers can use to break out of that specific variable and assign values to other arbitrary variables. Workflows that write untrusted values to theGITHUB_ENVfile may cause the path or other environment variables to be modified without the intention of the workflow or action author.Patches
Users should upgrade to
@actions/core v1.9.1.Workarounds
If you are unable to upgrade the
@actions/corepackage, you can modify your action to ensure that any user input does not contain the delimiter_GitHubActionsFileCommandDelimeter_before callingcore.exportVariable.References
More information about setting-an-environment-variable in workflows
If you have any questions or comments about this advisory:
actions/toolkitRelease Notes
actions/toolkit (@actions/core)
v1.9.1core.exportVariablev1.9.0toPosixPath,toWin32PathandtoPlatformPathutilities #1102v1.8.2@actions/http-client#1087v1.8.1@actions/http-clientv1.8.0markdownSummaryextension export in favor ofsummaryv1.7.0markdownSummaryextensionv1.6.0getIDTokenfileparameter toAnnotationPropertiesv1.5.0v1.4.0getMultilineInputfunctionv1.3.0v1.2.7v1.2.6exportVariableandaddPathto use environment filesv1.2.5Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.