Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🚨 [security] Update mocha-github-actions-reporter 0.3.0 → 0.3.1 (minor) #6406

Merged
merged 1 commit into from
Jan 25, 2024

Conversation

depfu[bot]
Copy link
Contributor

@depfu depfu bot commented Jan 25, 2024


🚨 Your current dependencies have known security vulnerabilities 🚨

This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!


Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ mocha-github-actions-reporter (0.2.4 → 0.3.1) · Repo

Commits

See the full diff on Github. The new version differs by 8 commits:

✳️ @​actions/core (1.4.0 → 1.9.1) · Repo · Changelog

Security Advisories 🚨

🚨 @actions/core has Delimiter Injection Vulnerability in exportVariable

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:

Release Notes

1.9.1 (from changelog)

  • Randomize delimiter when calling core.exportVariable

1.9.0 (from changelog)

  • Added toPosixPath, toWin32Path and toPlatformPath utilities #1102

1.8.2 (from changelog)

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

1.8.1 (from changelog)

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

1.8.0 (from changelog)

  • Deprecate markdownSummary extension export in favor of summary

1.7.0 (from changelog)

1.6.0 (from changelog)

1.5.0 (from changelog)

Does any of this look wrong? Please let us know.


Depfu Status

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands
@​depfu rebase
Rebases against your default branch and redoes this update
@​depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@​depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@​depfu cancel merge
Cancels automatic merging of this PR
@​depfu close
Closes this PR and deletes the branch
@​depfu reopen
Restores the branch and reopens this PR (if it's closed)
@​depfu pause
Ignores all future updates for this dependency and closes this PR
@​depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@​depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)

@depfu depfu bot added the depfu label Jan 25, 2024
@depfu depfu bot requested a review from a team January 25, 2024 08:50
@cla-bot cla-bot bot added the cla: yes label Jan 25, 2024
@kraenhansen kraenhansen self-assigned this Jan 25, 2024
@kraenhansen
Copy link
Member

@​depfu merge

@depfu depfu bot merged commit fcf570f into main Jan 25, 2024
34 checks passed
@depfu depfu bot deleted the depfu/update/npm/mocha-github-actions-reporter-0.3.1 branch January 25, 2024 09:58
bimusiek pushed a commit to bimusiek/realm-js that referenced this pull request Mar 14, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 14, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant