Skip to content

GitHub Actions expression injection vulnerability in CheckIssueForCodeFormatting workflow

Moderate
Mytherin published GHSA-7q92-pph9-5686 Jul 23, 2024

Package

No package listed

Affected versions

no release version was affected

Patched versions

None

Description

Summary

Pull request #10149 introduced a GitHub Actions expression injection vulnerability, potentially allowing an attacker to take over the repository.

Details

There is a vulnerability in Line 24 of .github/workflow/CheckIssueForCodeFormatting.yml, where the ${{ github.event.issue.body }} entry is directly used in the run statement. This design allows for the execution of arbitrary commands if a malicious issue is submitted. Consequently, an attacker could compromise the GitHub Runner, thereby accessing sensitive CI secrets such as GH_TOKEN and GITHUB_TOKEN. Therefore, the attacker can push arbitrary code to the repository using the GITHUB_TOKEN.

Impact

We have searched through the entire issue log of the duckdb repository (including the history of the issue bodies) for potential abuses of this vulnerability and have found that this has not been exploited. The vulnerability was patched via PR #11522. No releases were affected by the vulnerability. There are no actions required of users.

Severity

Moderate

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 v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:H

CVE ID

No known CVE

Weaknesses

No CWEs

Credits