skip to content
Back to
Home Bounties Research Advisories CodeQL Wall of Fame Get Involved Events
February 3, 2021

GHSL-2021-004: Arbitrary code execution in aeraki workflows

Jaroslav Lobacevski

Coordinated Disclosure Timeline


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.


aeraki-framework/aeraki repository

Tested Version

The latest changesets e2e-dubbo.yaml, e2e-thrift.yaml and e2e-kafka-zookeeper.yaml to the date.


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.

      - '**.md'
      - 'docs/**'
        uses: actions/checkout@v2
          ref: ${{ github.event.pull_request.head.ref }}
          repository: ${{ github.event.pull_request.head.repo.full_name }}
        run: make docker-build-e2e


The vulnerability allows for unauthorized modification of the base repository and secrets exfiltration.


This issue was discovered and reported by GHSL team member @JarLob (Jaroslav Lobačevski).


You can contact the GHSL team at, please include a reference to GHSL-2021-004 in any communication regarding this issue.