CVE-2025-23203
Vulnerability from cvelistv5
Published
2025-03-26 13:44
Modified
2025-03-26 13:44
Severity ?
EPSS score ?
Summary
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.3 and 1.11.3 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.3 and 1.11.1. If upgrading is not feasible, disable the director module for the users other than admin role for the time being.
References
Impacted products
Vendor | Product | Version | ||
---|---|---|---|---|
Icinga | icingaweb2-module-director |
Version: >= 1.0.0, < 1.10.3 Version: >= 1.11.0, < 1.11.3 |
{ containers: { cna: { affected: [ { product: "icingaweb2-module-director", vendor: "Icinga", versions: [ { status: "affected", version: ">= 1.0.0, < 1.10.3", }, { status: "affected", version: ">= 1.11.0, < 1.11.3", }, ], }, ], descriptions: [ { lang: "en", value: "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.3 and 1.11.3 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.3 and 1.11.1. If upgrading is not feasible, disable the director module for the users other than admin role for the time being.", }, ], metrics: [ { cvssV3_1: { attackComplexity: "LOW", attackVector: "NETWORK", availabilityImpact: "NONE", baseScore: 5.5, baseSeverity: "MEDIUM", confidentialityImpact: "HIGH", integrityImpact: "LOW", privilegesRequired: "HIGH", scope: "UNCHANGED", userInteraction: "NONE", vectorString: "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:L/A:N", version: "3.1", }, }, ], problemTypes: [ { descriptions: [ { cweId: "CWE-200", description: "CWE-200: Exposure of Sensitive Information to an Unauthorized Actor", lang: "en", type: "CWE", }, ], }, { descriptions: [ { cweId: "CWE-284", description: "CWE-284: Improper Access Control", lang: "en", type: "CWE", }, ], }, ], providerMetadata: { dateUpdated: "2025-03-26T13:44:58.110Z", orgId: "a0819718-46f1-4df5-94e2-005712e83aaa", shortName: "GitHub_M", }, references: [ { name: "https://github.com/Icinga/icingaweb2-module-director/security/advisories/GHSA-3233-ggc5-m3qg", tags: [ "x_refsource_CONFIRM", ], url: "https://github.com/Icinga/icingaweb2-module-director/security/advisories/GHSA-3233-ggc5-m3qg", }, { name: "https://github.com/Icinga/icingaweb2-module-director/releases/tag/v1.10.3", tags: [ "x_refsource_MISC", ], url: "https://github.com/Icinga/icingaweb2-module-director/releases/tag/v1.10.3", }, { name: "https://github.com/Icinga/icingaweb2-module-director/releases/tag/v1.11.3", tags: [ "x_refsource_MISC", ], url: "https://github.com/Icinga/icingaweb2-module-director/releases/tag/v1.11.3", }, ], source: { advisory: "GHSA-3233-ggc5-m3qg", discovery: "UNKNOWN", }, title: "Icinga has rest API endpoints accessible to restricted users", }, }, cveMetadata: { assignerOrgId: "a0819718-46f1-4df5-94e2-005712e83aaa", assignerShortName: "GitHub_M", cveId: "CVE-2025-23203", datePublished: "2025-03-26T13:44:58.110Z", dateReserved: "2025-01-13T17:15:41.050Z", dateUpdated: "2025-03-26T13:44:58.110Z", state: "PUBLISHED", }, dataType: "CVE_RECORD", dataVersion: "5.1", "vulnerability-lookup:meta": { nvd: "{\"cve\":{\"id\":\"CVE-2025-23203\",\"sourceIdentifier\":\"security-advisories@github.com\",\"published\":\"2025-03-26T14:15:32.250\",\"lastModified\":\"2025-03-27T16:45:27.850\",\"vulnStatus\":\"Awaiting Analysis\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"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.3 and 1.11.3 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.3 and 1.11.1. If upgrading is not feasible, disable the director module for the users other than admin role for the time being.\"},{\"lang\":\"es\",\"value\":\"Icinga Director es una herramienta de implementación de configuración de Icinga. Se ha detectado una vulnerabilidad de seguridad a partir de la versión 1.0.0 y anteriores a las 1.10.3 y 1.11.3 en varios directores endpoints de la API REST. Para reproducir esta vulnerabilidad, se requiere un usuario autenticado con permiso de acceso a Director (además de acceso a la API en relación con los endpoints de la API). Aunque algunos de estos usuarios de Icinga Director tienen restringido el acceso a ciertos objetos, pueden recuperar información relacionada con ellos si se conoce su nombre. Esto permite que los usuarios de Icinga Director con acceso restringido modifiquen la configuración de estos objetos. Esto da lugar a una mayor explotación, filtraciones de datos y divulgación de información confidencial. Los endpoints afectados incluyen icingaweb2/director/service (si el nombre de host no se incluye en la consulta); icingaweb2/directore/notification; icingaweb2/director/serviceset; e icingaweb2/director/scheduled-downtime. Además, el endpoint `icingaweb2/director/services?host=filteredHostName` devuelve un código de estado 200, aunque los servicios del host estén filtrados. Esto, a su vez, informa al usuario restringido de que el host `filteredHostName` existe, aunque tenga restringido el acceso. Esto podría provocar una mayor explotación de esta información y filtraciones de datos. Icinga Director cuenta con parches en las versiones 1.10.3 y 1.11.1. Si no es posible actualizar, deshabilite el módulo director para los usuarios que no tengan rol de administrador por el momento.\"}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"security-advisories@github.com\",\"type\":\"Secondary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:L/A:N\",\"baseScore\":5.5,\"baseSeverity\":\"MEDIUM\",\"attackVector\":\"NETWORK\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"HIGH\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"HIGH\",\"integrityImpact\":\"LOW\",\"availabilityImpact\":\"NONE\"},\"exploitabilityScore\":1.2,\"impactScore\":4.2}]},\"weaknesses\":[{\"source\":\"security-advisories@github.com\",\"type\":\"Primary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-200\"},{\"lang\":\"en\",\"value\":\"CWE-284\"}]}],\"references\":[{\"url\":\"https://github.com/Icinga/icingaweb2-module-director/releases/tag/v1.10.3\",\"source\":\"security-advisories@github.com\"},{\"url\":\"https://github.com/Icinga/icingaweb2-module-director/releases/tag/v1.11.3\",\"source\":\"security-advisories@github.com\"},{\"url\":\"https://github.com/Icinga/icingaweb2-module-director/security/advisories/GHSA-3233-ggc5-m3qg\",\"source\":\"security-advisories@github.com\"}]}}", }, }
Log in or create an account to share your comment.
Security Advisory comment format.
This schema specifies the format of a comment related to a security advisory.
Title of the comment
Description of the comment
Loading…
Loading…
Loading…
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.