Skip to content

Insecure path traversal in Git Trigger Source can lead to arbitrary file read

High severity GitHub Reviewed Published Jun 13, 2022 in argoproj/argo-events • Updated Aug 28, 2023

Package

gomod github.com/argoproj/argo-events (Go)

Affected versions

< 1.7.1

Patched versions

1.7.1

Description

Impact

A path traversal issue was found in the (g *GitArtifactReader).Read() API. Read() calls into (g *GitArtifactReader).readFromRepository() that opens and reads the file that contains the trigger resource definition:

func (g *GitArtifactReader) readFromRepository(r *git.Repository, dir string)

No checks are made on this file at read time, which could lead an attacker to read files anywhere on the system. This could be achieved by either using symbolic links, or putting ../ in the path.

Patches

A patch for this vulnerability has been released in the following Argo Events version:

v1.7.1

Credits

Disclosed by Ada Logics in a security audit sponsored by CNCF and facilitated by OSTIF.

For more information

Open an issue in the Argo Events issue tracker or discussions
Join us on Slack in channel #argo-events

References

@whynowy whynowy published to argoproj/argo-events Jun 13, 2022
Published to the GitHub Advisory Database Jun 17, 2022
Reviewed Jun 17, 2022
Published by the National Vulnerability Database Jun 17, 2022
Last updated Aug 28, 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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
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:N/UI:N/S:U/C:H/I:N/A:N

EPSS score

0.184%
(57th percentile)

Weaknesses

CVE ID

CVE-2022-25856

GHSA ID

GHSA-qpgx-64h2-gc3c

Source code

Credits

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