# CVE-2022-25856: Directory Traversal

> Attackers can read arbitrary files via directory traversal in the GitArtifactReader API of the Argo Events Go library.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Jun 2022
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-qpgx-64h2-gc3c, GO-2022-0492, SNYK-GOLANG-GITHUBCOMARGOPROJARGOEVENTSSENSORSARTIFACTS-2864522

## What is CVE-2022-25856?

CVE-2022-25856 is a high-severity path traversal vulnerability in github.com/argoproj/argo-events/sensors/artifacts, published on 17 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The package github.com/argoproj/argo-events/sensors/artifacts before 1.7.1 are vulnerable to Directory Traversal in the (g *GitArtifactReader).Read() API in git.go. This could allow arbitrary file reads if the GitArtifactReader is provided a pathname containing a symbolic link or an implicit directory name such as ...

Weakness: CWE-59 (Improper Link Resolution Before File Access), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2022-25856?

3 open source packages ship an affected version, including github.com/argoproj/argo-events. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/argoproj/argo-events` | Go | All versions | 1.7.1 |
| `github.com/argoproj/argo-events` | Go | All versions | 1.7.1 |
| `github.com/argoproj/argo-events` | Go | All versions | 1.7.1 |

Products: Argo Events Project Argo Events.

## How do I fix CVE-2022-25856?

Upgrade github.com/argoproj/argo-events to 1.7.1 or later.

## Is CVE-2022-25856 being exploited?

There is no known exploitation of CVE-2022-25856 in the wild and no public exploit code.

## Other vulnerabilities in github.com/argoproj/argo-events/sensors/artifacts

- [CVE-2022-31054](https://insights.sbomify.com/CVE-2022-31054/): Uses of deprecated API can be used to cause DoS in user-facing endpoints in Argo Events (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-25856 and fix it if it is affected.

What it is: CVE-2022-25856 is a high-severity path traversal vulnerability in github.com/argoproj/argo-events/sensors/artifacts, published on 17 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-25856 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/argoproj/argo-events (Go): affected all versions; fixed in 1.7.1
- github.com/argoproj/argo-events (Go): affected all versions; fixed in 1.7.1
- github.com/argoproj/argo-events (Go): affected all versions; fixed in 1.7.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-25856/ (Markdown: https://insights.sbomify.com/CVE-2022-25856/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-25856
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-25856
- OSV: https://osv.dev/vulnerability/CVE-2022-25856

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-25856/
Summaries are generated and may contain mistakes; the official description above is the record.