[Security Vulnerability] Run build with unit tests without elevated permissions #47
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
masivesky
force-pushed
the
sec-vuln-fix-develop
branch
2 times, most recently
from
8fad5eb to
54339c9
Compare
checkstyle.xml
Outdated
| <!-- | ||
| Copyright © 2014-2023 Cask Data, Inc. | ||
| Copyright © 2014-2015 Cask Data, Inc. |
itsankit-google
approved these changes
Sep 11, 2024
masivesky
force-pushed
the
sec-vuln-fix-develop
branch
from
54339c9 to
22f9b3c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fix for security vulnerability:
This change prevents any external contributor to create another workflow in the PR with same name as Trigger Build which allow it to run the Build With Unit Tests with elevated permissions.
It uses Github Hosted Runners to build the surefire report with elevated permissions.