Update gradle/gradle-build-action action to v2 [SECURITY] - autoclosed #33
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:
v1.5.0
->v2.4.2
GitHub Vulnerability Alerts
CVE-2023-30853
Impact
This vulnerability impacts GitHub workflows using the Gradle Build Action that have executed the Gradle Build Tool with the configuration cache enabled, potentially exposing secrets configured for the repository.
Secrets configured for GitHub Actions are normally passed to the Gradle Build Tool via environment variables. Due to the way that the Gradle Build Tool records these environment variables, they may be persisted into an entry in the GitHub Actions cache. This data stored in the GitHub Actions cache can be read by a GitHub Actions workflow running in an untrusted context, such as that running for a Pull Request submitted by a developer via a repository fork.
This vulnerability was discovered internally through code review, and we have not seen any evidence of it being exploited in the wild. However, in addition to upgrading the Gradle Build Action, you should delete any potentially vulnerable cache entries and may choose to rotate any potentially affected secrets (see Remediation).
Patches
Gradle Build Action v2.4.2 (and newer) no longer save this sensitive data for later use, preventing ongoing leakage of secrets via the GitHub Actions Cache. We strongly recommend that all users of the Gradle Build Action upgrade to
v2.4.2
(or simplyv2
) immediately.Remediation
While upgrading to the latest version of the Gradle Build Action will prevent leakage of secrets going forward, additional actions may be required due to current or previous GitHub Actions Cache entries containing this information.
Current cache entries will remain vulnerable until they are forcibly deleted or they expire naturally after 7 days of not being used. Potentially vulnerable entries can be easily identified in the GitHub UI by searching for a cache entry with key matching
configuration-cache-*
. We recommend that users of the Gradle Build Action inspect their list of cache entries and manually delete any that match this pattern.While we have not seen any evidence of this vulnerability being exploited, we recommend cycling any repository secrets if you cannot be certain that these have not been compromised. Compromise could occur if you run a GitHub Actions workflow for a pull request attempting to exploit this data.
Warning signs to look for in a pull request include:
Workarounds
We strongly recommend that all users upgrade to the latest version of the Gradle Build Action as soon as possible, and delete any potentially vulnerable cache entries from the GitHub Actions cache (see Remediation).
If for some reason this is not possible, users can limit the impact of this vulnerability:
--no-configuration-cache
command-line argument can be used to disable this feature in a GitHub Actions workflow.In any case, we recommend that users carefully inspect any pull request before approving the execution of GitHub Actions workflows. It may be prudent to require approval for all PRs from external contributors, as described here.
Release Notes
gradle/gradle-build-action (gradle/gradle-build-action)
v2.4.2
Compare Source
This release disables the save/restore of configuration-cache data, since this functionality has been shown to be problematic.
Gradle 8.1 has made changes to this functionality which will require a more comprehensive rework of the action before we can re-enable this.
v2.4.1
Compare Source
This patch release updates a number of dependencies, including
xmljs
which was reported to have a security vulnerability (https://nvd.nist.gov/vuln/detail/CVE-2023-0842).There is no evidence that this vulnerability affected the
gradle-build-action
.Full changelog: gradle/gradle-build-action@v2.4.0...v2.4.1
v2.4.0
Compare Source
What's new
The
v.2.4.0
release contains various library updates and fixes to fully support Gradle 8.Notable changes:
@actions/cache: 3.1.3
should improve cache save/restore performance on Windows by using gnu tar and zstd when available.e444647
)Full Changelog: gradle/gradle-build-action@v2.3.3...v2.4.0
v2.3.3
Compare Source
This patch release removes all uses of the deprecated
set-output
andset-state
commands, and should remove deprecation warnings from build logs. See #461 and #477 for more details.Full Changelog: gradle/gradle-build-action@v2.3.2...v2.3.3
v2.3.2
Compare Source
This patch release fixes an issue which could result in errors in the post-action step. See #441 for details.
Full Changelog: gradle/gradle-build-action@v2.3.1...v2.3.2
v2.3.1
Compare Source
This patch release addresses some security vulnerabilities reported by the CodeQL check:
sourcemap-register.js
: this triggered Incorrect suffix check@azure/logger
library to avoid logging an environment variable value: this triggered Clear-text logging of sensitive informationThe release contains no functional changes.
Full Changelog: gradle/gradle-build-action@v2.3.0...v2.3.1
v2.3.0
Compare Source
What's new
With
v2.3.0
, thegradle-build-action
can now attempt to remove any unused files from the Gradle User Home directory before storing to the GitHub Actions cache. This can prevent cases where the size of cache entry grows over time.Gradle Home cache cleanup is disabled by default. You can enable this feature for the action as follows:
See the README for more details.
Full Changelog: gradle/gradle-build-action@v2.2.5...v2.3.0
v2.2.5
Compare Source
What's fixed
Fixes a bug where a corrupted cache entry caused an error in
beforeSave
(#408). This meant that the entry was never purged.By allowing
@actions/globber
to follow symlinks and ignore broken symlinks, the bad files in the cache entry are ignored and the corrupted cache entry can be replaced by a good one.Full Changelog: gradle/gradle-build-action@v2.2.4...v2.2.5
v2.2.4
Compare Source
What's fixed
The fix for #383 introduced a bug that caused the post-action to fail when attempting to resolve cache-read-only for scheduled jobs.
This has been fixed with an explicit (rather than implicit) check for 'event.repository != null'. (#409)
Full Changelog: gradle/gradle-build-action@v2.2.3...v2.2.4
v2.2.3
Compare Source
What's fixed
This release updates a number of key dependencies and fixes some cache-related issues:
cache-read-only=true
for scheduled workflows on default branch (#383)v2.2.2
(#407)Full Changelog: gradle/gradle-build-action@v2.2.2...v2.2.3
v2.2.2
Compare Source
What's fixed
This release fixes some issues that were discovered in the
v2.2.1
release, and updates a number of dependencies.Full Changelog: gradle/gradle-build-action@v2.2.1...v2.2.2
v2.2.1
Compare Source
What's fixed
This release fixes some issues that were exposed by the
v2.2.0
release, as well as improving the content and layout of the Job Summary.Entry not saved: reason unknown
message in Job Summary cache details: #309Full Changelog: gradle/gradle-build-action@v2.2.0...v2.2.1
v2.2.0
Compare Source
Summary
This release brings a new Job Summary report, as well as numerous improvements and bug fixes:
cache-read-only
for non-default branches (see0a36ca9
)Issues resolved
https://github.com/gradle/gradle-build-action/milestone/7?closed=1
What's Changed
cache-read-only
for non-default branches by @bigdaz in https://github.com/gradle/gradle-build-action/pull/149Full Changelog: gradle/gradle-build-action@v2.1.7...v2.2.0
v2.1.7
Compare Source
Fixes #293, which prevented
v2.1.6
from allowing Gradle to re-use previously downloaded wrapper distributions. This slowed down build executions and could result in build flakiness when the wrapper zip failed to download.wrapper
folder of Gradle User Home, avoiding re-download of wrapper distributions.v2.1.6
Compare Source
This release contains an fix for changed behaviour in Gradle 7.6, as well as numerous library upgrades.
Earlier versions of the
gradle-build-action
were saving and restoring the downloaded Gradle wrapper zip file as part of caching the Gradle User Home. This will no longer work with Gradle 7.6, as the wrapper zip is now removed after expanding. This release ofgradle-build-action
contains a fix for this change in Gradle 7.6. Using an older version of the GitHub action with Gradle 7.6 will likely result in the wrapper being downloaded on every GitHub actions invocation.What's Changed
@actions/core
,@actions/cache
,@actions/github
,@actions/http-client
and@actions/tool-cache
.Full changelog: gradle/gradle-build-action@v2.1.5...v2.1.6
v2.1.5
Compare Source
This release addresses a potential security issue by upgrading
minimist
, and fixes a bug with very large cache entries by upgrading@actions/cache
. No other changes are included.What's Changed
Full changelog: gradle/gradle-build-action@v2.1.4...v2.1.5
v2.1.4
Compare Source
What's Changed
d700906
.Full Changelog: gradle/gradle-build-action@v2.1.3...v2.1.4
v2.1.3
Compare Source
This patch release fixes an issue that prevented the Gradle User Home from being restored from cache on
macos-latest
runners. #155What's Changed
Full Changelog: gradle/gradle-build-action@v2.1.2...v2.1.3
v2.1.2
Compare Source
This patch release fixes a minor bug and updates some NPM dependencies, including one dependency with a reported security advisory.
What's Changed
gradle.properties
is no longer overwritten by action initializationnode-fetch
to a version that isn't impacted by GHSA-r683-j2x4-v87g. Note that this CVE has been determined not to impact the action.Full Changelog: gradle/gradle-build-action@v2.1.1...v2.1.2
v2.1.1
Compare Source
This release improves logging and fixes a number of minor issues.
gradlew
script is not executable #76In addition, 2 experimental configuration parameters have been added:
gradle-home-cache-strict-match
: Only reuse cache entries generated by previous invocations for the same jobcache-write-only
: Do not restore cache entries but save on Job completionFull Changelog: gradle/gradle-build-action@v2.1.0...v2.1.1
v2.1.0
Compare Source
Overview
This release brings a major improvement in usability, allowing the action to be used to "setup Gradle" without requiring all Gradle invocations to be managed by the action.
Any Gradle invocation after the first
gradle-build-action
step will benefit from caching and build-scan capture just as if it was invoked through a subsequentgradle-build-action
. This is achieved viainit
scripts added when initializing/restoring the Gradle User Home.This change makes it easier to adopt the
gradle-build-action
into an existing GitHub Actions workflow and enables usages such as:Usability improvements
run
step to invoke Gradle and still benefit from Gradle User Home caching as well as build-scan integration.Caching improvements
Changes in detail
Full Changelog: gradle/gradle-build-action@v2.0.0...v2.1.0
v2.0.1
Compare Source
What's Changed
This patch release fixes a couple of cases where a failure to store caches would cause the entire Job to fail. The goal of the
gradle-build-action
is to warn-and-continue on all recoverable cache failures.Issues fixed
Full Changelog: gradle/gradle-build-action@v2.0.0...v2.0.1
v2.0.0
Compare Source
This is the initial release of
gradle-build-action@v2
, which brings significant performance and usability improvements overv1
. A few key improvements are outlined here, but see the project README for more details.Thanks for trying it out!
Usability improvements:
The
gradle-build-action
has been redesigned from the ground up to work well with minimal configuration, avoiding the need for most users to tweak multiple configuration options to benefit.Highlights:
Notice
annotations to your workflow run.Performance improvements:
A key benefit of
gradle-build-action
over other solutions is the sophisticated support for saving and restoring relevant Gradle state between build invocations. This caching support speeds up build invocations and is designed to work in most scenarios without further tweaking.Highlights:
v1.5.1
Compare Source
Fixes issue where invalid cache keys could be generated if the Gradle arguments list was overly long.
Configuration
📅 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.