Approved changes feed: RSS · Atom
cpe:2.3:a:toolkit_project:toolkit:*:*:*:*:*:node.js:*:*part: a version: * update: *
| Vendor | Toolkit Project (f1c93fb9-5480-548d-8977-2314c5608037) |
|---|---|
| Product | Toolkit (a4f211a9-d324-5a36-bc85-da946948caba) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | node.js |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2020-15228 |
vulnerable | 2026-06-08 05:19:25.549232 |
Environment Variable Injection in GitHub Actions
LOW (3.5)
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: 2020-10-01T17:25:12.000Z
Updated: 2024-08-04T13:08:22.896Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.