[fix] [ci] update gha file to mitigate Fork Network Manipulation vuln #545
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.
What this PR does / why we need it:
Currently, the way ci pipeline is setup, exposes a risk for Fork Network Manipulation ultimately achieving remote code execution. This happens as a result of the way we are setting up environments based on forked repos.
As a result, the attacker gains control over the workflow, giving them access to the GitHub Actions Cache. This allows the attacker to, via a Cache Poisoning attack, compromise over workflows to gain write-all access to the repository, and control over the certain repo/org secrets.
We are now explicitly requiring that the prod environment be used on PR only when the repo name matches this repo, and not forked repos in GHA runs