Skip to content

⬆️ Updates @actions/core to v1.9.1 [SECURITY] - #626

Open
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/npm-actions-core-vulnerability
Open

renovate[bot] wants to merge 1 commit into
masterfrom
renovate/npm-actions-core-vulnerability

Conversation

@renovate

@renovate renovate Bot commented Aug 6, 2024 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
@actions/core (source) 1.2.6 → 1.9.1 age confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


@​actions/core has Delimiter Injection Vulnerability in exportVariable

CVE-2022-35954 / GHSA-7r3h-m5j6-3q42

More information

Details

Impact

The core.exportVariable function 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 the GITHUB_ENV file 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/core package, you can modify your action to ensure that any user input does not contain the delimiter _GitHubActionsFileCommandDelimeter_ before calling core.exportVariable.

References

More information about setting-an-environment-variable in workflows

If you have any questions or comments about this advisory:

Severity

  • CVSS Score: 5.0 / 10 (Medium)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:N

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


Release Notes

actions/toolkit (@​actions/core)

v1.9.1

  • Randomize delimiter when calling core.exportVariable

v1.9.0

  • Added toPosixPath, toWin32Path and toPlatformPath utilities #​1102

v1.8.2

  • Update to v2.0.1 of @actions/http-client #​1087

v1.8.1

  • Update to v2.0.0 of @actions/http-client

v1.8.0

  • Deprecate markdownSummary extension export in favor of summary

v1.7.0

v1.6.0

v1.5.0

v1.4.0

v1.3.0

v1.2.7


Configuration

📅 Schedule: (in timezone Europe/Moscow)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ 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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate

renovate Bot commented Aug 6, 2024

Copy link
Copy Markdown
Contributor Author

Branch automerge failure

This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.


  • Branch has one or more failed status checks

@auto-assign
auto-assign Bot requested a review from AlexRogalskiy August 6, 2024 11:19
@github-actions

github-actions Bot commented Aug 6, 2024

Copy link
Copy Markdown

Thanks for the PR!

This section of the codebase is owner by https://github.com/AlexRogalskiy/ - if they write a comment saying "LGTM" then it will be merged.

@github-actions

github-actions Bot commented Aug 6, 2024

Copy link
Copy Markdown

🏷️ [bumpr] Next version:v2.0.2 Changes:v2.0.1...AlexRogalskiy:renovate/npm-actions-core-vulnerability

@renovate
renovate Bot force-pushed the renovate/npm-actions-core-vulnerability branch from c18e43d to f60893d Compare January 23, 2025 19:36
@renovate
renovate Bot force-pushed the renovate/npm-actions-core-vulnerability branch from f60893d to 7db7df9 Compare March 3, 2025 21:07
@renovate
renovate Bot force-pushed the renovate/npm-actions-core-vulnerability branch from 7db7df9 to 3edb366 Compare April 1, 2025 08:56
@renovate
renovate Bot force-pushed the renovate/npm-actions-core-vulnerability branch from 3edb366 to 49a1397 Compare November 11, 2025 01:15
@renovate
renovate Bot force-pushed the renovate/npm-actions-core-vulnerability branch from 49a1397 to 2be409b Compare November 20, 2025 19:39
@renovate renovate Bot changed the title ⬆️ Updates @actions/core to v1.9.1 [SECURITY] ⬆️ Updates @actions/core to v1.9.1 [SECURITY] - autoclosed Mar 27, 2026
@renovate renovate Bot closed this Mar 27, 2026
@renovate
renovate Bot deleted the renovate/npm-actions-core-vulnerability branch March 27, 2026 01:05
@renovate renovate Bot changed the title ⬆️ Updates @actions/core to v1.9.1 [SECURITY] - autoclosed ⬆️ Updates @actions/core to v1.9.1 [SECURITY] Mar 30, 2026
@renovate renovate Bot reopened this Mar 30, 2026
@renovate
renovate Bot force-pushed the renovate/npm-actions-core-vulnerability branch from 2be409b to 6c537e7 Compare March 30, 2026 22:06
@renovate
renovate Bot force-pushed the renovate/npm-actions-core-vulnerability branch from 6c537e7 to 2bf9268 Compare April 18, 2026 10:06
@renovate renovate Bot changed the title ⬆️ Updates @actions/core to v1.9.1 [SECURITY] ⬆️ Updates @actions/core to v1.9.1 [SECURITY] - autoclosed Apr 27, 2026
@renovate renovate Bot closed this Apr 27, 2026
@renovate renovate Bot changed the title ⬆️ Updates @actions/core to v1.9.1 [SECURITY] - autoclosed ⬆️ Updates @actions/core to v1.9.1 [SECURITY] Apr 27, 2026
@renovate renovate Bot reopened this Apr 27, 2026
@renovate
renovate Bot force-pushed the renovate/npm-actions-core-vulnerability branch 2 times, most recently from 2bf9268 to 918d517 Compare April 27, 2026 21:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants