Coordinated Disclosure Timeline
- 2021-01-18: Report sent to maintainer.
- 2021-01-22: Maintainer acknowledges.
- 2021-01-23: Issue resolved.
Summary
The e2e-thrift.yaml, e2e-dubbo.yaml and e2e-kafka-zookeeper.yaml GitHub workflows are vulnerable to unauthorized modification of the base repository or secrets exfiltration from a Pull Request.
Product
aeraki-framework/aeraki repository
Tested Version
The latest changesets e2e-dubbo.yaml, e2e-thrift.yaml and e2e-kafka-zookeeper.yaml to the date.
Details
Issue: Untrusted code is explicitly checked out and run on a Pull Request from a fork
Workflows triggered on pull_request_target have read/write tokens for the base repository and the access to secrets. By explicitly checking out and running the build script from a fork the untrusted code is running in an environment that is able to push to the base repository and to access secrets. More details can be found in the article Keeping your GitHub Actions and workflows secure: Preventing pwn requests.
on:
pull_request_target:
paths-ignore:
- '**.md'
- 'docs/**'
...
uses: actions/checkout@v2
with:
ref: ${{ github.event.pull_request.head.ref }}
repository: ${{ github.event.pull_request.head.repo.full_name }}
...
run: make docker-build-e2e
Impact
The vulnerability allows for unauthorized modification of the base repository and secrets exfiltration.
Credit
This issue was discovered and reported by GHSL team member @JarLob (Jaroslav Lobačevski).
Contact
You can contact the GHSL team at securitylab@github.com, please include a reference to GHSL-2021-004 in any communication regarding this issue.