Skip to content

pr-e2e.yml workflow is vulnerable

Low
JorTurFer published GHSA-w92x-gx4w-j5f2 Jul 26, 2023

Package

gomod e2e tests (Go)

Affected versions

v2.11

Patched versions

v2.11.2

Description

Summary

The pr-e2e.yml workflow is vulnerable to command injection attacks because of using an untrusted event.comment.body field.

Details

Line 140: MESSAGE="${{ github.event.comment.body }}"

PoC

Assigning the value of the issue comment body to any-body"; echo hacked can lead to command injection.

Impact

Since the permission is not restricted, the attacker has a write-access to the repository.

Severity

Low

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
High
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

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:H/UI:R/S:U/C:L/I:N/A:N

CVE ID

No known CVE

Weaknesses

Credits