@actions core up to 1.2.5 on npm addPath/exportVariable input validation

Summaryinfo

A vulnerability categorized as problematic has been discovered in @actions core up to 1.2.5 on npm. Impacted is the function addPath/exportVariable. The manipulation results in input validation. This vulnerability is identified as CVE-2020-15228. The attack can be executed remotely. There is not any exploit available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as problematic, was found in @actions core up to 1.2.5 on npm. Affected is the function addPath/exportVariable. The manipulation with an unknown input leads to a input validation vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality. CVE summarizes:

In the `@actions/core` npm module before version 1.2.6,`addPath` and `exportVariable` functions communicate with the Actions Runner over stdout by generating a string in a specific format. Workflows that log untrusted data to stdout may invoke these commands, resulting in the path or environment variables being modified without the intention of the workflow or action author. The runner will release an update that disables the `set-env` and `add-path` workflow commands in the near future. For now, users should upgrade to `@actions/core v1.2.6` or later, and replace any instance of the `set-env` or `add-path` commands in their workflows with the new Environment File Syntax. Workflows and actions using the old commands or older versions of the toolkit will start to warn, then error out during workflow execution.

The weakness was released 10/01/2020 (GitHub Repository). The advisory is shared for download at github.com. This vulnerability is traded as CVE-2020-15228 since 06/25/2020. The exploitability is told to be difficult. It is possible to launch the attack remotely. The successful exploitation needs a authentication. There are known technical details, but no exploit is available.

Upgrading to version 1.2.6 eliminates this vulnerability.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

• NPM Package

Name

• @actions core

Version

• 1.2.0
• 1.2.1
• 1.2.2
• 1.2.3
• 1.2.4
• 1.2.5

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion