Skip to content

Rest API endpoints accessible to restricted users

Moderate
raviks789 published GHSA-3233-ggc5-m3qg Mar 26, 2025

Package

Icinga Director (Icinga)

Affected versions

>=1.0.0

Patched versions

1.10.3, 1.11.3

Description

Impact

A Security vulnerability has been found 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:

  • icingaweb2/director/service, if the host name is left out of the query (Example: icingaweb2/director/service?name=service-name)
  • icingaweb2/directore/notification
  • icingaweb2/director/serviceset
  • 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.

Solution

Icinga Director will receive minor updates to the 1.10 and 1.11 branches to remedy this issue.

Upgrade immediately to a patched release. If that is not feasible, disable the director module for the users other than admin role for the time being.

References

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

CWE-284: Improper Access Control

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:L/A:N

CVE ID

CVE-2025-23203

Weaknesses

Exposure of Sensitive Information to an Unauthorized Actor

The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Learn more on MITRE.

Improper Access Control

The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. Learn more on MITRE.