# CVE-2022-24714: Disclosure of hosts and related data, linked to decommissioned services in Icinga Web 2

> Users with specific roles may retain access to decommissioned service data in Icinga Web 2, leading to information disclosure.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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-24714, GHSA-qcmg-vr56-x9wf, UBUNTU-CVE-2022-24714

## What is CVE-2022-24714?

CVE-2022-24714 is a medium-severity 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. Installations of Icinga 2 with the IDO writer enabled are affected. If you use service custom variables in role restrictions, and you regularly decommission service objects, users with said roles may still have access to a collection of content. Note that this only applies if a role has implicitly permitted access to hosts, due to permitted access to at least one of their services. If access to a host is permitted by other means, no sensible information has been disclosed to unauthorized users. This issue has been resolved in versions 2.8.6, 2.9.6 and 2.10 of Icinga Web 2.

Weakness: CWE-863 (Incorrect Authorization)

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

It affects 1 product.


Products: Icinga Icinga Web 2.

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

Upgrade to a fixed version.

## Is CVE-2022-24714 being exploited?

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

## 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-2022-24716](https://insights.sbomify.com/CVE-2022-24716/): Path traversal in Icinga Web 2 (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-24714 is a medium-severity 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: There is no known exploitation of CVE-2022-24714 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-24714/ (Markdown: https://insights.sbomify.com/CVE-2022-24714/index.md)
```

## Sources

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

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