chore(deps): update dependency @actions/core to v1.9.1 [security] #245
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.6.0->1.9.1GitHub Vulnerability Alerts
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/toolkit@actions/core has Delimiter Injection Vulnerability in exportVariable
CVE-2022-35954 / GHSA-7r3h-m5j6-3q42
More information
Details
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/toolkitSeverity
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:NReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
Release 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.0markdownSummaryextensionConfiguration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
Need help?
You can ask for more help in the following Slack channel: #proj-renovate-self-hosted. In that channel you can also find ADR and FAQ docs in the Resources section.