# CVE-2022-31054: Uses of deprecated API can be used to cause DoS in user-facing endpoints in Argo Events

> Attackers can crash Argo Events servers by sending large requests to endpoints using deprecated memory-intensive APIs, causing denial of service.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Jun 2022
- **Updated:** 23 Apr 2025
- **Also known as:** GHSA-5q86-62xr-3r57, GO-2022-0490

## What is CVE-2022-31054?

CVE-2022-31054 is a high-severity denial of service vulnerability in argoproj argo-events, published on 13 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Argo Events is an event-driven workflow automation framework for Kubernetes. Prior to version 1.7.1, several `HandleRoute` endpoints make use of the deprecated `ioutil.ReadAll()`. `ioutil.ReadAll()` reads all the data into memory. As such, an attacker who sends a large request to the Argo Events server will be able to crash it and cause denial of service. A patch for this vulnerability has been released in Argo Events version 1.7.1.

Weakness: CWE-787 (Out-of-bounds Write), CWE-400 (Uncontrolled Resource Consumption)

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

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-31054?

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

## Is CVE-2022-31054 being exploited?

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

## Other vulnerabilities in argoproj argo-events

- [CVE-2022-25856](https://insights.sbomify.com/CVE-2022-25856/): Directory Traversal (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-31054 is a high-severity denial of service vulnerability in argoproj argo-events, published on 13 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-31054 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-31054/ (Markdown: https://insights.sbomify.com/CVE-2022-31054/index.md)
```

## Sources

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

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