# CVE-2022-24715: Arbitrary code execution for authenticated users in Icinga Web 2

> Authenticated users can exploit path traversal to create SSH resource files in unintended directories, leading to arbitrary code execution.

- **Severity:** High 8.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **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:** 8 Mar 2022
- **Updated:** 23 Apr 2025
- **Also known as:** DEBIAN-CVE-2022-24715, GHSA-v9mv-h52f-7g63, UBUNTU-CVE-2022-24715

## What is CVE-2022-24715?

CVE-2022-24715 is a high-severity path traversal vulnerability in icingaweb2, published on 8 Mar 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Icinga Web 2 is an open source monitoring web interface, framework and command-line interface. Authenticated users, with access to the configuration, can create SSH resource files in unintended directories, leading to the execution of arbitrary code. This issue has been resolved in versions 2.8.6, 2.9.6 and 2.10 of Icinga Web 2. Users unable to upgrade should limit access to the Icinga Web 2 configuration.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Icinga Icinga Web 2.

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

Upgrade to a fixed version.

## Is CVE-2022-24715 being exploited?

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

Public exploit code:

-  Authenticated Remote Code Execution in Icinga Web 2 <2.8.6, <2.9.6, <2.10 (github_poc): https://github.com/nimphtix/CVE-2022-24715
- Icinga Web 2 - Authenticated Remote Code Execution <2.8.6, <2.9.6, <2.10 (github_poc): https://github.com/cxdxnt/CVE-2022-24715
- Icinga Web 2.10 - Authenticated Remote Code Execution (exploitdb)
- https://github.com/d4rkb0n3/CVE-2022-24715-go (github_poc): https://github.com/d4rkb0n3/CVE-2022-24715-go

## Other vulnerabilities in icingaweb2

- [CVE-2018-18249](https://insights.sbomify.com/CVE-2018-18249/): Code injection in n/a (critical 9.8)
- [CVE-2025-27404](https://insights.sbomify.com/CVE-2025-27404/): Icinga Web 2 DOM-based XSS vulnerability (high 7.7)
- [CVE-2025-27405](https://insights.sbomify.com/CVE-2025-27405/): Icinga Web 2 has XSS in embedded content (high 7.7)
- [CVE-2022-24716](https://insights.sbomify.com/CVE-2022-24716/): Path traversal in Icinga Web 2 (high 7.5)
- [CVE-2018-18250](https://insights.sbomify.com/CVE-2018-18250/): Other in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-24715 is a high-severity path traversal vulnerability in icingaweb2, published on 8 Mar 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-24715 in the wild and no public exploit code.

Affected product: icingaweb2. 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-2022-24715/ (Markdown: https://insights.sbomify.com/CVE-2022-24715/index.md)
```

## Sources

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

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