CVE Intelligence
Skip to main content
LOWpublic exploit

CVE-2020-15228

CVE-2020-15228 — Environment Variable Injection in GitHub Actions

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.

Published Updated Sources: cvelistV5, GitHub_M

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Exploit code

public exploit, none observed

EPSS

1%

chance of exploitation in 30 days

Affects

actions

toolkit

CVSS base

3.5

LOW

Affected scope

The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.

Vendors (1)

actions

Products (1)

toolkit

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactSource
3.5CVSS 3.1LOW——cvelistV5

Weakness & attack patterns

  • CWE-20

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

  • T1562.003Impair Defenses: Impair Command History Logging
  • T1574.006Hijack Execution Flow: Dynamic Linker Hijacking
  • T1574.007Hijack Execution Flow: Path Interception by PATH Environment Variable

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Indexed by

poc in github

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

  • Search application, proxy, and WAF logs for requests touching /core.

References

2 on the record

Elsewhere on this site

  • actionsevery CVE for this vendor
  • CWE-20other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.