CVE-2023-52137: Tj actions/verify changed files Potential Actions Command Injection Vulnerability

HIGH
Advisory Identifier: GHSA-ghm2-rq8q-wrhc
CVSS 7.7
CWE-20 CWE-77
Published
Advisory Summary

CVE-2023-52137 is a HIGH (CVSS 7.7) potential actions command injection vulnerability (CWE-20: Improper Input Validation) affecting Tj actions/verify changed files libraries in the GitHub Actions ecosystem. The issue involves potential actions command injection in output filenames (ghsl-2023-275). Remediation is available by upgrading affected packages to version 17.

CVE-2023-52137 at a Glance

CVE Identifier CVE-2023-52137
GHSA Identifier GHSA-ghm2-rq8q-wrhc
Severity HIGH
CVSS v3.1 Base Score 7.7
CWE Classification CWE-20: Improper Input Validation
Affected Product Tj actions/verify changed files
Package Ecosystem GitHub Actions
Published Date
Last Updated

Security Impact

CVSS: 7.7

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:L).

Attack Vector Network (AV:N)
Attack Complexity High (AC:H)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Changed (S:C)
Confidentiality High (C:H)
Integrity Low (I:L)
Availability Low (A:L)

How to Fix CVE-2023-52137

To remediate this vulnerability, upgrade all affected Tj actions/verify changed files dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

tj-actions/verify-changed-files fixed: 17
Upgrade tj-actions/verify-changed-files to 17
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for tj-actions/verify-changed-files

How to Check if You Are Affected

To determine whether your application is affected by CVE-2023-52137, inspect your project dependencies for Tj actions/verify changed files:

inspect dependencies for tj-actions/verify-changed-files

Analyze the terminal output to locate any version of Tj actions/verify changed files in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 17), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-20: Improper Input Validation, where the product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. In Tj actions/verify changed files, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary The [`tj-actions/verify-changed-files`](https://github.com/tj-actions/verify-changed-files) action allows for command injection in changed filenames, allowing an attacker to execute arbitrary code and potentially leak secrets. ### Details The [`verify-changed-files`](https://github.com/tj-actions/verify-changed-files) workflow returns the list of files changed within a workflow execution. This could potentially allow filenames that contain special characters such as `;` and \` (backtick) which can be used by an attacker to take over the [GitHub Runner](https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners) if the output value is used in a raw fashion (thus being directly replaced before execution) inside a `run` block. By running custom commands an attacker may be able to steal **secrets** such as `GITHUB_TOKEN` if triggered on other events than `pull_request`. For example on `push`. #### Proof of Concept 1. Submit a pull request to the repository with a new file injecting a command. For example `$(whoami).txt` would be a valid filename. 2. Upon approval of the workflow (triggered by the pull request), the action will get executed and the malicious pull request filename will flow into the `List all changed files tracked and untracked files` step. ```yaml - name: List all changed files tracked and untracked files run: | echo "Changed files: ${{ steps.verify-changed-files.outputs.changed_files }}" ``` Example output: ```yaml ##[group]Run echo "Changed files: $(whoami).txt" echo "Changed files: $(whoami).txt" shell: /usr/bin/bash -e {0} ##[endgroup] Changed files: runner.txt ``` ### Impact This issue may lead to arbitrary command execution in the GitHub Runner. ### Resolution - A new `safe_output` input would be enabled by default and return filename paths escaping special characters like ;, ` (backtick), $, (), etc for bash environments. - A safe recommendation of using environment variables to store unsafe outputs. ```yaml - name: List all changed files tracked and untracked files env: CHANGED_FILES: ${{ steps.verify-changed-files.outputs.changed_files }} run: | echo "Changed files: $CHANGED_FILES" ``` ### Resources * [Keeping your GitHub Actions and workflows secure Part 2: Untrusted input](https://securitylab.github.com/research/github-actions-untrusted-input/) * [Keeping your GitHub Actions and workflows secure Part 1: Preventing pwn requests](https://securitylab.github.com/research/github-actions-preventing-pwn-requests/)

CVE-2023-52137 Affected Tj actions/verify changed files Versions

1 component(s)
Fixed Versions:
17
Product / Package Ecosystem Affected Versions Fixed Version
tj-actions/verify-changed-files
GitHub Actions
< 17
17

References

Frequently Asked Questions

What is CVE-2023-52137?
CVE-2023-52137 is a security vulnerability in Tj actions/verify changed files involving Potential Actions command injection in output filenames (GHSL-2023-275) under CWE-20: Improper Input Validation.
Which Tj actions/verify changed files versions are affected?
Affected versions include releases prior to 17 across affected packages: tj-actions/verify-changed-files.
What version fixes CVE-2023-52137?
Upgrading to 17 (or the latest patched release for your respective branch) resolves the vulnerability.
Is tj-actions/verify-changed-files affected?
Yes, tj-actions/verify-changed-files is affected in releases prior to 17. Upgrade your dependency to 17 or later.
What is the CVSS score of CVE-2023-52137?
CVE-2023-52137 has a CVSS v3.1 base score of 7.7 (HIGH) with vector string CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:L.
What CWE is associated with CVE-2023-52137?
CVE-2023-52137 is classified under CWE-20: Improper Input Validation (The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.).
How can I check GitHub Actions dependencies for CVE-2023-52137?
Run the dependency tree command: 'inspect dependencies for tj-actions/verify-changed-files'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-ghm2-rq8q-wrhc",
  "modified" : "2024-01-02T16:42:27Z",
  "published" : "2024-01-02T16:42:27Z",
  "aliases" : [ "CVE-2023-52137" ],
  "summary" : "Potential Actions command injection in output filenames (GHSL-2023-275)",
  "details" : "### Summary\nThe [`tj-actions/verify-changed-files`](https://github.com/tj-actions/verify-changed-files) action allows for command injection in changed filenames, allowing an attacker to execute arbitrary code and potentially leak secrets.\n\n### Details\nThe [`verify-changed-files`](https://github.com/tj-actions/verify-changed-files) workflow returns the list of files changed within a workflow execution.\n\nThis could potentially allow filenames that contain special characters such as `;` and \\` (backtick) which can be used by an attacker to take over the [GitHub Runner](https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners) if the output value is used in a raw fashion (thus being directly replaced before execution) inside a `run` block. By running custom commands an attacker may be able to steal **secrets** such as `GITHUB_TOKEN` if triggered on other events than `pull_request`. For example on `push`.\n\n#### Proof of Concept\n\n1. Submit a pull request to the repository with a new file injecting a command. For example `$(whoami).txt` would be a valid filename.\n2. Upon approval of the workflow (triggered by the pull request), the action will get executed and the malicious pull request filename will flow into the `List all changed files tracked and untracked files` step.\n\n```yaml\n- name: List all changed files tracked and untracked files\n  run: |\n    echo \"Changed files: ${{ steps.verify-changed-files.outputs.changed_files }}\"\n```\n\nExample output:\n\n```yaml\n##[group]Run echo \"Changed files: $(whoami).txt\"\n  echo \"Changed files: $(whoami).txt\"\u001B[0m\nshell: /usr/bin/bash -e {0}\n##[endgroup]\nChanged files: runner.txt\n```\n\n### Impact\nThis issue may lead to arbitrary command execution in the GitHub Runner.\n\n### Resolution\n- A new `safe_output` input would be enabled by default and return filename paths escaping special characters like ;, ` (backtick), $, (), etc for bash environments.\n\n- A safe recommendation of using environment variables to store unsafe outputs.\n\n```yaml\n- name: List all changed files tracked and untracked files\n  env:\n     CHANGED_FILES: ${{ steps.verify-changed-files.outputs.changed_files }}\n  run: |\n    echo \"Changed files: $CHANGED_FILES\"\n```\n\n\n### Resources\n\n* [Keeping your GitHub Actions and workflows secure Part 2: Untrusted input](https://securitylab.github.com/research/github-actions-untrusted-input/)\n* [Keeping your GitHub Actions and workflows secure Part 1: Preventing pwn requests](https://securitylab.github.com/research/github-actions-preventing-pwn-requests/)\n",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:L"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "GitHub Actions",
      "name" : "tj-actions/verify-changed-files"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "17"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/tj-actions/verify-changed-files/security/advisories/GHSA-ghm2-rq8q-wrhc"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2023-52137"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/tj-actions/verify-changed-files/commit/498d3f316f501aa72485060e8c96fde7b2014f12"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/tj-actions/verify-changed-files/commit/592e305da041c09a009afa4a43c97d889bed65c3"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/tj-actions/verify-changed-files"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-20", "CWE-77" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2024-01-02T16:42:27Z",
    "nvd_published_at" : "2023-12-29T17:16:07Z"
  }
}