GitHub Actions Runner up to 2.296.1 os command injection

Summaryinfo

A vulnerability labeled as critical has been found in GitHub Actions Runner up to 2.283.3/2.285.1/2.289.3/2.293.0/2.296.1. The impacted element is an unknown function. The manipulation results in os command injection. This vulnerability was named CVE-2022-39321. The attack may be performed from remote. There is no available exploit. The affected component should be upgraded.

Detailsinfo

A vulnerability was found in GitHub Actions Runner up to 2.283.3/2.285.1/2.289.3/2.293.0/2.296.1 (Bug Tracking Software). It has been classified as critical. Affected is an unknown part. The manipulation with an unknown input leads to a os command injection vulnerability. CWE is classifying the issue as CWE-78. The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:

GitHub Actions Runner is the application that runs a job from a GitHub Actions workflow. The actions runner invokes the docker cli directly in order to run job containers, service containers, or container actions. A bug in the logic for how the environment is encoded into these docker commands was discovered in versions prior to 2.296.2, 2.293.1, 2.289.4, 2.285.2, and 2.283.4 that allows an input to escape the environment variable and modify that docker command invocation directly. Jobs that use container actions, job containers, or service containers alongside untrusted user inputs in environment variables may be vulnerable. The Actions Runner has been patched, both on `github.com` and hotfixes for GHES and GHAE customers in versions 2.296.2, 2.293.1, 2.289.4, 2.285.2, and 2.283.4. GHES and GHAE customers may want to patch their instance in order to have their runners automatically upgrade to these new runner versions. As a workaround, users may consider removing any container actions, job containers, or service containers from their jobs until they are able to upgrade their runner versions.

The weakness was presented 10/25/2022 as GHSA-2c6m-6gqh-6qg3. The advisory is shared for download at github.com. This vulnerability is traded as CVE-2022-39321 since 09/02/2022. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1202.

Upgrading to version 2.283.4, 2.285.2, 2.289.4, 2.293.1 or 2.296.2 eliminates this vulnerability. Applying a patch 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.

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Productinfo

Type

• Bug Tracking Software

Vendor

• GitHub

Name

• Actions Runner

Version

• 2.283.0
• 2.283.1
• 2.283.2
• 2.283.3
• 2.285.0
• 2.285.1
• 2.289.0
• 2.289.1
• 2.289.2
• 2.289.3
• 2.293
• 2.296.0
• 2.296.1

License

• open-source

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Discussion