You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are currently maintaining a fork of this repository. Upon integrating a gradle wrapper validation action into our Continuous Integration (CI) process, we discovered an inconsistency with the gradle-wrapper.jar file present in this project. The SHA256 checksum of the gradle-wrapper.jar file does not match the official checksum provided on the Gradle website. This discrepancy raises concerns regarding the integrity and security of the Gradle wrapper used in this project, potentially exposing it to security risks.
To reproduce
Add uses: gradle/wrapper-validation-action@v2 to your gha workflow in order to check gradle wrapper
The text was updated successfully, but these errors were encountered:
helloncode
changed the title
Gradle wrapper jar not recognized Gradle Validation Action
Gradle wrapper jar not recognized by Gradle Wrapper Validation Action
Feb 5, 2024
Braintree SDK Version
6.14.0
Environment
Production
Android Version & Device
No response
Braintree dependencies
None
Describe the bug
Security Vulnerability Report: gradle-wrapper.jar SHA256 Mismatch
Description:
We are currently maintaining a fork of this repository. Upon integrating a gradle wrapper validation action into our Continuous Integration (CI) process, we discovered an inconsistency with the
gradle-wrapper.jar
file present in this project. The SHA256 checksum of thegradle-wrapper.jar
file does not match the official checksum provided on the Gradle website. This discrepancy raises concerns regarding the integrity and security of the Gradle wrapper used in this project, potentially exposing it to security risks.To reproduce
Add
uses: gradle/wrapper-validation-action@v2
to your gha workflow in order to check gradle wrapperExpected behavior
uses: gradle/wrapper-validation-action@v2
shouldn't failsScreenshots
No response
The text was updated successfully, but these errors were encountered: