# CVE-2024-34155: Stack exhaustion in all Parse functions in go/parser

> Attackers can cause a denial of service by providing Go source code with deeply nested literals to the parser, leading to stack exhaustion and application panic.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Sep 2024
- **Updated:** 4 Nov 2024
- **Also known as:** AZL-48896, AZL-78988, AZL-98886, BELL-CVE-2024-34155, BIT-golang-2024-34155, DEBIAN-CVE-2024-34155, ECHO-e851-3ecb-a213, GHSA-8xfx-rj4p-23jm, GO-2024-3105, MINI-2h3c-hh8m-8593, MINI-9vm4-7x96-jrv5, OESA-2024-2398, UBUNTU-CVE-2024-34155, openSUSE-SU-2024:14392-1

## What is CVE-2024-34155?

CVE-2024-34155 is a medium-severity denial of service vulnerability in go/parser, published on 6 Sep 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Calling any of the Parse functions on Go source code which contains deeply nested literals can cause a panic due to stack exhaustion.

## Which versions are affected by CVE-2024-34155?

2 open source packages ship an affected version, including golang and stdlib.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `golang` | Bitnami | All versions | 1.22.7, 1.23.1 |
| `stdlib` | Go | All versions | 1.22.7, 1.23.1 |
| `trivy` | openSUSE:Tumbleweed | All versions | 0.56.1-1.1 |

## How do I fix CVE-2024-34155?

Upgrade golang to a fixed version for your release line: 1.22.7 or 1.23.1.

## Is CVE-2024-34155 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-34155 and fix it if it is affected.

What it is: CVE-2024-34155 is a medium-severity denial of service vulnerability in go/parser, published on 6 Sep 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-34155 in the wild and no public exploit code.

Affected packages and fixed versions:
- golang (Bitnami): affected all versions; fixed in 1.22.7, 1.23.1
- stdlib (Go): affected all versions; fixed in 1.22.7, 1.23.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-2024-34155/ (Markdown: https://insights.sbomify.com/CVE-2024-34155/index.md)
```

## Sources

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

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