# CVE-2024-22029: tomcat packaging allows for escalation to root from tomcat user

> Local attackers can escalate to root privileges by winning a race condition during Tomcat package installation due to insecure permissions.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Oct 2024
- **Updated:** 26 Aug 2025
- **Also known as:** GHSA-w8vw-x82m-vg68, SUSE-SU-2024:0473-1, openSUSE-SU-2024:13692-1, openSUSE-SU-2024:13693-1

## What is CVE-2024-22029?

CVE-2024-22029 is a high-severity vulnerability in Container suse/manager/5.0/x86_64/server:5.0.0-beta1.2.122, published on 16 Oct 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Insecure permissions in the packaging of tomcat allow local users that win a race during package installation to escalate to root

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `tomcat10` | SUSE:Linux Enterprise Module for Web and Scripting 15 SP5 | All versions | 10.1.18-150200.5.11.1 |
| `tomcat10` | openSUSE:Leap 15.5 | All versions | 10.1.18-150200.5.11.1 |
| `tomcat` | openSUSE:Tumbleweed | All versions | 9.0.85-3.1 |
| `tomcat10` | openSUSE:Tumbleweed | All versions | 10.1.18-3.1 |

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

Apply the vendor's patch.

## Is CVE-2024-22029 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-22029 is a high-severity vulnerability in Container suse/manager/5.0/x86_64/server:5.0.0-beta1.2.122, published on 16 Oct 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-22029 in the wild and no public exploit code.

Affected product: Container suse/manager/5.0/x86_64/server:5.0.0-beta1.2.122. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-22029/ (Markdown: https://insights.sbomify.com/CVE-2024-22029/index.md)
```

## Sources

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

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