tj-actions verify-changed-files up to 16.x input validation

Summaryinfo

A vulnerability, which was classified as problematic, has been found in tj-actions verify-changed-files up to 16.x. The impacted element is an unknown function. This manipulation causes input validation. This vulnerability is registered as CVE-2023-52137. Remote exploitation of the attack is possible. No exploit is available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability classified as problematic was found in tj-actions verify-changed-files up to 16.x. Affected by this vulnerability is an unknown functionality. The manipulation with an unknown input leads to a input validation vulnerability. The CWE definition for the vulnerability is CWE-20. 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. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

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. 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 `;` 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`. This has been patched in versions [17](https://github.com/tj-actions/verify-changed-files/releases/tag/v17) and [17.0.0](https://github.com/tj-actions/verify-changed-files/releases/tag/v17.0.0) by enabling `safe_output` by default and returning filename paths escaping special characters for bash environments.

The weakness was published 12/29/2023 as GHSA-ghm2-rq8q-wrhc. It is possible to read the advisory at github.com. This vulnerability is known as CVE-2023-52137 since 12/28/2023. The technical details are unknown and an exploit is not publicly available.

Upgrading to version 17.0.0 eliminates this vulnerability. Applying the patch 498d3f316f501aa72485060e8c96fde7b2014f12 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Vendor

• tj-actions

Name

• verify-changed-files

Version

• 16.x

License

• open-source

Website

• Product: https://github.com/tj-actions/verify-changed-files/

CPE 2.3info

• 🔍

CPE 2.2info

• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion