# CVE-2025-23203: Icinga has rest API endpoints accessible to restricted users

> Restricted Icinga Director users can access and modify configuration objects they should not see, leading to information disclosure and unauthorized changes.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Mar 2025
- **Updated:** 20 Jan 2026
- **Also known as:** DEBIAN-CVE-2025-23203, GHSA-3233-ggc5-m3qg, UBUNTU-CVE-2025-23203

## What is CVE-2025-23203?

CVE-2025-23203 is a medium-severity missing authorization vulnerability in icingaweb2-module-director, published on 26 Mar 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Icinga Director is an Icinga config deployment tool. A Security vulnerability has been found starting in version 1.0.0 and prior to 1.10.4 and 1.11.4 on several director endpoints of REST API. To reproduce this vulnerability an authenticated user with permission to access the Director is required (plus api access with regard to the api endpoints). And even though some of these Icinga Director users are restricted from accessing certain objects, are able to retrieve information related to them if their name is known. This makes it possible to change the configuration of these objects by those Icinga Director users restricted from accessing them. This results in further exploitation, data breaches and sensitive information disclosure. Affected endpoints include icingaweb2/director/service, if the host name is left out of the query; icingaweb2/directore/notification; icingaweb2/director/serviceset; and icingaweb2/director/scheduled-downtime. In addition, the endpoint `icingaweb2/director/services?host=filteredHostName` returns a status code 200 even though the services for the host is filtered. This in turn lets the restricted user know that the host `filteredHostName` exists even though the user is restricted from accessing it.  This could again result in further exploitation of this information and data breaches. Icinga Director has patches in versions 1.10.4 and 1.11.4. If upgrading is not feasible, disable the director module for the users other than admin role for the time being.

Weakness: CWE-284 (Improper Access Control), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2025-23203?


## How do I fix CVE-2025-23203?

Upgrade to a fixed version.

## Is CVE-2025-23203 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-23203 and fix it if it is affected.

What it is: CVE-2025-23203 is a medium-severity missing authorization vulnerability in icingaweb2-module-director, published on 26 Mar 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-23203 in the wild and no public exploit code.

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

## Sources

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

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