# CVE-2022-24716: Path traversal in Icinga Web 2

> Unauthenticated attackers can read local system files, including database credentials, via path traversal in Icinga Web 2.

- **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:** 8 Mar 2022
- **Updated:** 23 Apr 2025
- **Also known as:** DEBIAN-CVE-2022-24716, GHSA-5p3f-rh28-8frw, UBUNTU-CVE-2022-24716

## What is CVE-2022-24716?

CVE-2022-24716 is a high-severity path traversal vulnerability in icingaweb2, published on 8 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Icinga Web 2 is an open source monitoring web interface, framework and command-line interface. Unauthenticated users can leak the contents of files of the local system accessible to the web-server user, including `icingaweb2` configuration files with database credentials. This issue has been resolved in versions 2.9.6 and 2.10 of Icinga Web 2. Database credentials should be rotated.

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

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

It affects 1 product.


Products: Icinga Icinga Web 2.

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

Upgrade to a fixed version.

## Is CVE-2022-24716 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-24716 exists.

Public exploit code:

- Arbitrary File Disclosure Vulnerability in Icinga Web 2 <2.8.6, <2.9.6, <2.10 (github_poc): https://github.com/0x0Jackal/CVE-2022-24716
- Icingaweb Directory Traversal in Static Library File Requests (metasploit)
- Arbitrary File Disclosure Vulnerability in Icinga Web 2 <2.8.6, <2.9.6, <2.10 (github_poc): https://github.com/gmh5225/CVE-2022-24716
- https://github.com/pumpkinpiteam/CVE-2022-24716 (github_poc): https://github.com/pumpkinpiteam/CVE-2022-24716
- Icinga Web 2.10 - Arbitrary File Disclosure (exploitdb)
- https://github.com/antisecc/CVE-2022-24716 (github_poc): https://github.com/antisecc/CVE-2022-24716

## Other vulnerabilities in icingaweb2

- [CVE-2018-18249](https://insights.sbomify.com/CVE-2018-18249/): Code injection in n/a (critical 9.8)
- [CVE-2022-24715](https://insights.sbomify.com/CVE-2022-24715/): Arbitrary code execution for authenticated users in Icinga Web 2 (high 8.5)
- [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-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-24716 and fix it if it is affected.

What it is: CVE-2022-24716 is a high-severity path traversal vulnerability in icingaweb2, published on 8 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-24716 exists.

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

## Sources

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

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