setup-php 2.37.0

Direct Vulnerabilities

Known vulnerabilities in the setup-php package. This does not include vulnerabilities belonging to this package’s dependencies.

Fix vulnerabilities automatically

Snyk's AI Trust Platform automatically finds the best upgrade path and integrates with your development workflows. Secure your code at zero cost.

Fix for free

Vulnerability	Vulnerable Version
M Command Injection setup-php is a Setup PHP for use with GitHub Actions Affected versions of this package are vulnerable to Command Injection via the process that resolves PHP version from repository-controlled files such as `.php-version`, `composer.lock`, or `composer.json` and incorporates the value into the generated setup script. An attacker can execute arbitrary commands on the GitHub Actions runner by injecting malicious values into these files when the workflow runs in a trusted context after checking out attacker-controlled repository contents. This is only exploitable if the workflow executes after checking out untrusted code and resolves the PHP version from repository files in a privileged context. How to fix Command Injection? Upgrade `setup-php` to version 2.37.1 or higher.	>=2.25.0 <2.37.1
H Insertion of Sensitive Information into Log File setup-php is a Setup PHP for use with GitHub Actions Affected versions of this package are vulnerable to Insertion of Sensitive Information into Log File via the `process` that configures GitHub tokens for Composer in workflows where an exact affected Composer version is pinned. An attacker can obtain sensitive authentication tokens by accessing public repository logs that may inadvertently expose these tokens during Composer's validation of github-oauth authentication, especially when Composer rejects GitHub's newer hyphen-containing token format. This is only exploitable if a workflow pins an exact affected Composer version through the process, rather than using the default or a patched Composer version. How to fix Insertion of Sensitive Information into Log File? Upgrade `setup-php` to version 2.37.1 or higher.	<2.37.1

Vulnerability

Vulnerable Version

Command Injection

setup-php is a Setup PHP for use with GitHub Actions

Affected versions of this package are vulnerable to Command Injection via the process that resolves PHP version from repository-controlled files such as .php-version, composer.lock, or composer.json and incorporates the value into the generated setup script. An attacker can execute arbitrary commands on the GitHub Actions runner by injecting malicious values into these files when the workflow runs in a trusted context after checking out attacker-controlled repository contents. This is only exploitable if the workflow executes after checking out untrusted code and resolves the PHP version from repository files in a privileged context.

How to fix Command Injection?

Upgrade setup-php to version 2.37.1 or higher.

>=2.25.0 <2.37.1

Insertion of Sensitive Information into Log File

setup-php is a Setup PHP for use with GitHub Actions

Affected versions of this package are vulnerable to Insertion of Sensitive Information into Log File via the process that configures GitHub tokens for Composer in workflows where an exact affected Composer version is pinned. An attacker can obtain sensitive authentication tokens by accessing public repository logs that may inadvertently expose these tokens during Composer's validation of github-oauth authentication, especially when Composer rejects GitHub's newer hyphen-containing token format. This is only exploitable if a workflow pins an exact affected Composer version through the process, rather than using the default or a patched Composer version.

How to fix Insertion of Sensitive Information into Log File?

Upgrade setup-php to version 2.37.1 or higher.

<2.37.1

setup-php@2.37.0

Setup PHP for use with GitHub Actions

latest version

latest non vulnerable version

first published

latest version published

licenses detected

Direct Vulnerabilities

Fix vulnerabilities automatically