Skip to content

run-terraform allows for RCE via terraform plan

High severity GitHub Reviewed Published Oct 19, 2022 in kartverket/github-workflows • Updated Jan 30, 2023

Package

actions kartverket/github-workflows (GitHub Actions)

Affected versions

< 2.7.5

Patched versions

2.7.5

Description

Impact

What kind of vulnerability is it? Who is impacted?
All users of the run-terraform reusable workflow from the kartverket/github-workflows repo are affected. A malicious actor could potentially send a PR with a malicious payload leading to execution of arbitrary JavaScript code in the context of the workflow.

Patches

Has the problem been patched? What versions should users upgrade to?
Upgrade to at least 2.7.5 to resolve the issue.

Workarounds

Is there a way for users to fix or remediate the vulnerability without upgrading?
Until you are able to upgrade, make sure to review any PRs from exernal users for malicious payloads before allowing them to trigger a build.

For more information

If you have any questions or comments about this advisory:

References

@eliihen eliihen published to kartverket/github-workflows Oct 19, 2022
Published to the GitHub Advisory Database Oct 19, 2022
Reviewed Oct 19, 2022
Published by the National Vulnerability Database Oct 25, 2022
Last updated Jan 30, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS score

0.203%
(58th percentile)

Weaknesses

CVE ID

CVE-2022-39326

GHSA ID

GHSA-f9qj-7gh3-mhj4

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.