{"containers": {"cna": {"affected": [{"product": "icingaweb2", "vendor": "Icinga", "versions": [{"status": "affected", "version": ">= 2.0.0, <= 2.8.2"}]}], "descriptions": [{"lang": "en", "value": "Icinga Web 2 is an open source monitoring web interface, framework, and command-line interface. A vulnerability in which custom variables are exposed to unauthorized users exists between versions 2.0.0 and 2.8.2. Custom variables are user-defined keys and values on configuration objects in Icinga 2. These are commonly used to reference secrets in other configurations such as check commands to be able to authenticate with a service being checked. Icinga Web 2 displays these custom variables to logged in users with access to said hosts or services. In order to protect the secrets from being visible to anyone, it's possible to setup protection rules and blacklists in a user's role. Protection rules result in `***` being shown instead of the original value, the key will remain. Backlists will hide a custom variable entirely from the user. Besides using the UI, custom variables can also be accessed differently by using an undocumented URL parameter. By adding a parameter to the affected routes, Icinga Web 2 will show these columns additionally in the respective list. This parameter is also respected when exporting to JSON or CSV. Protection rules and blacklists however have no effect in this case. Custom variables are shown as-is in the result. The issue has been fixed in the 2.9.0, 2.8.3, and 2.7.5 releases. As a workaround, one may set up a restriction to hide hosts and services with the custom variable in question."}], "metrics": [{"cvssV3_1": {"attackComplexity": "HIGH", "attackVector": "NETWORK", "availabilityImpact": "NONE", "baseScore": 5.3, "baseSeverity": "MEDIUM", "confidentialityImpact": "HIGH", "integrityImpact": "NONE", "privilegesRequired": "LOW", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/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"}]}], "providerMetadata": {"dateUpdated": "2021-07-12T22:50:11", "orgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "shortName": "GitHub_M"}, "references": [{"tags": ["x_refsource_MISC"], "url": "https://github.com/Icinga/icingaweb2/releases/tag/v2.7.5"}, {"tags": ["x_refsource_MISC"], "url": "https://github.com/Icinga/icingaweb2/releases/tag/v2.8.3"}, {"tags": ["x_refsource_MISC"], "url": "https://github.com/Icinga/icingaweb2/releases/tag/v2.9.0"}, {"tags": ["x_refsource_CONFIRM"], "url": "https://github.com/Icinga/icingaweb2/security/advisories/GHSA-2xv9-886q-p7xx"}], "source": {"advisory": "GHSA-2xv9-886q-p7xx", "discovery": "UNKNOWN"}, "title": "Custom variable protection and blacklists can be circumvented", "x_legacyV4Record": {"CVE_data_meta": {"ASSIGNER": "[email protected]", "ID": "CVE-2021-32747", "STATE": "PUBLIC", "TITLE": "Custom variable protection and blacklists can be circumvented"}, "affects": {"vendor": {"vendor_data": [{"product": {"product_data": [{"product_name": "icingaweb2", "version": {"version_data": [{"version_value": ">= 2.0.0, <= 2.8.2"}]}}]}, "vendor_name": "Icinga"}]}}, "data_format": "MITRE", "data_type": "CVE", "data_version": "4.0", "description": {"description_data": [{"lang": "eng", "value": "Icinga Web 2 is an open source monitoring web interface, framework, and command-line interface. A vulnerability in which custom variables are exposed to unauthorized users exists between versions 2.0.0 and 2.8.2. Custom variables are user-defined keys and values on configuration objects in Icinga 2. These are commonly used to reference secrets in other configurations such as check commands to be able to authenticate with a service being checked. Icinga Web 2 displays these custom variables to logged in users with access to said hosts or services. In order to protect the secrets from being visible to anyone, it's possible to setup protection rules and blacklists in a user's role. Protection rules result in `***` being shown instead of the original value, the key will remain. Backlists will hide a custom variable entirely from the user. Besides using the UI, custom variables can also be accessed differently by using an undocumented URL parameter. By adding a parameter to the affected routes, Icinga Web 2 will show these columns additionally in the respective list. This parameter is also respected when exporting to JSON or CSV. Protection rules and blacklists however have no effect in this case. Custom variables are shown as-is in the result. The issue has been fixed in the 2.9.0, 2.8.3, and 2.7.5 releases. As a workaround, one may set up a restriction to hide hosts and services with the custom variable in question."}]}, "impact": {"cvss": {"attackComplexity": "HIGH", "attackVector": "NETWORK", "availabilityImpact": "NONE", "baseScore": 5.3, "baseSeverity": "MEDIUM", "confidentialityImpact": "HIGH", "integrityImpact": "NONE", "privilegesRequired": "LOW", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N", "version": "3.1"}}, "problemtype": {"problemtype_data": [{"description": [{"lang": "eng", "value": "CWE-200: Exposure of Sensitive Information to an Unauthorized Actor"}]}]}, "references": {"reference_data": [{"name": "https://github.com/Icinga/icingaweb2/releases/tag/v2.7.5", "refsource": "MISC", "url": "https://github.com/Icinga/icingaweb2/releases/tag/v2.7.5"}, {"name": "https://github.com/Icinga/icingaweb2/releases/tag/v2.8.3", "refsource": "MISC", "url": "https://github.com/Icinga/icingaweb2/releases/tag/v2.8.3"}, {"name": "https://github.com/Icinga/icingaweb2/releases/tag/v2.9.0", "refsource": "MISC", "url": "https://github.com/Icinga/icingaweb2/releases/tag/v2.9.0"}, {"name": "https://github.com/Icinga/icingaweb2/security/advisories/GHSA-2xv9-886q-p7xx", "refsource": "CONFIRM", "url": "https://github.com/Icinga/icingaweb2/security/advisories/GHSA-2xv9-886q-p7xx"}]}, "source": {"advisory": "GHSA-2xv9-886q-p7xx", "discovery": "UNKNOWN"}}}, "adp": [{"providerMetadata": {"orgId": "af854a3a-2127-422b-91ae-364da2661108", "shortName": "CVE", "dateUpdated": "2024-08-03T23:33:55.787Z"}, "title": "CVE Program Container", "references": [{"tags": ["x_refsource_MISC", "x_transferred"], "url": "https://github.com/Icinga/icingaweb2/releases/tag/v2.7.5"}, {"tags": ["x_refsource_MISC", "x_transferred"], "url": "https://github.com/Icinga/icingaweb2/releases/tag/v2.8.3"}, {"tags": ["x_refsource_MISC", "x_transferred"], "url": "https://github.com/Icinga/icingaweb2/releases/tag/v2.9.0"}, {"tags": ["x_refsource_CONFIRM", "x_transferred"], "url": "https://github.com/Icinga/icingaweb2/security/advisories/GHSA-2xv9-886q-p7xx"}]}]}, "cveMetadata": {"assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "assignerShortName": "GitHub_M", "cveId": "CVE-2021-32747", "datePublished": "2021-07-12T22:50:11", "dateReserved": "2021-05-12T00:00:00", "dateUpdated": "2024-08-03T23:33:55.787Z", "state": "PUBLISHED"}, "dataType": "CVE_RECORD", "dataVersion": "5.1"}

{}

{"configurations": [{"nodes": [{"cpeMatch": [{"criteria": "cpe:2.3:a:icinga:icinga:*:*:*:*:*:*:*:*", "matchCriteriaId": "6F5B4A77-A5AA-4417-8274-55784B0964D8", "versionEndExcluding": "2.7.5", "versionStartIncluding": "2.0.0", "vulnerable": true}, {"criteria": "cpe:2.3:a:icinga:icinga:*:*:*:*:*:*:*:*", "matchCriteriaId": "67125902-BF14-40DA-B319-88903781FA12", "versionEndExcluding": "2.8.3", "versionStartIncluding": "2.8.0", "vulnerable": true}], "negate": false, "operator": "OR"}]}], "descriptions": [{"lang": "en", "value": "Icinga Web 2 is an open source monitoring web interface, framework, and command-line interface. A vulnerability in which custom variables are exposed to unauthorized users exists between versions 2.0.0 and 2.8.2. Custom variables are user-defined keys and values on configuration objects in Icinga 2. These are commonly used to reference secrets in other configurations such as check commands to be able to authenticate with a service being checked. Icinga Web 2 displays these custom variables to logged in users with access to said hosts or services. In order to protect the secrets from being visible to anyone, it's possible to setup protection rules and blacklists in a user's role. Protection rules result in `***` being shown instead of the original value, the key will remain. Backlists will hide a custom variable entirely from the user. Besides using the UI, custom variables can also be accessed differently by using an undocumented URL parameter. By adding a parameter to the affected routes, Icinga Web 2 will show these columns additionally in the respective list. This parameter is also respected when exporting to JSON or CSV. Protection rules and blacklists however have no effect in this case. Custom variables are shown as-is in the result. The issue has been fixed in the 2.9.0, 2.8.3, and 2.7.5 releases. As a workaround, one may set up a restriction to hide hosts and services with the custom variable in question."}, {"lang": "es", "value": "Icinga Web 2 es una interfaz web de monitoreo de c\u00f3digo abierto, un marco de trabajo y una interfaz de l\u00ednea de comandos. Una vulnerabilidad entre las versiones 2.0.0 y 2.8.2, se presenta en la que las variables personalizadas son expuestas a usuarios no autorizados. Las variables personalizadas son claves y valores definidos por el usuario en los objetos de configuraci\u00f3n de Icinga 2. Estas son com\u00fanmente usadas para referenciar secretos en otras configuraciones tales como comandos de comprobaci\u00f3n para poder autenticarse con un servicio que est\u00e1 siendo comprobado. Icinga Web 2 muestra estas variables personalizadas a los usuarios registrados con acceso a dichos hosts o servicios. Para proteger que los secretos sean visibles para cualquiera, es posible configurar reglas de protecci\u00f3n y listas negras en el rol de un usuario. Las reglas de protecci\u00f3n resultan en que se muestre \"***\" en lugar del valor original, la clave permanecer\u00e1. Unas listas negras ocultar\u00e1n una variable personalizada por completo al usuario. Adem\u00e1s de utilizar la interfaz de usuario, tambi\u00e9n se puede acceder a las variables personalizadas de forma diferente usando un par\u00e1metro de URL no documentado. Al a\u00f1adir un par\u00e1metro a las rutas afectadas, Icinga Web 2 mostrar\u00e1 estas columnas adicionalmente en la lista respectiva. Este par\u00e1metro es tambi\u00e9n respetado al exportar a JSON o CSV. Sin embargo, las reglas de protecci\u00f3n y las listas negras no tienen efecto en este caso. Las variables personalizadas se muestran tal cual en el resultado. Este problema ha sido corregido en las versiones 2.9.0, 2.8.3 y 2.7.5. Como soluci\u00f3n alternativa, se puede ajustar una restricci\u00f3n para ocultar hosts y servicios con la variable personalizada en cuesti\u00f3n"}], "id": "CVE-2021-32747", "lastModified": "2024-11-21T06:07:39.730", "metrics": {"cvssMetricV2": [{"acInsufInfo": false, "baseSeverity": "MEDIUM", "cvssData": {"accessComplexity": "LOW", "accessVector": "NETWORK", "authentication": "SINGLE", "availabilityImpact": "NONE", "baseScore": 4.0, "confidentialityImpact": "PARTIAL", "integrityImpact": "NONE", "vectorString": "AV:N/AC:L/Au:S/C:P/I:N/A:N", "version": "2.0"}, "exploitabilityScore": 8.0, "impactScore": 2.9, "obtainAllPrivilege": false, "obtainOtherPrivilege": false, "obtainUserPrivilege": false, "source": "[email protected]", "type": "Primary", "userInteractionRequired": false}], "cvssMetricV31": [{"cvssData": {"attackComplexity": "HIGH", "attackVector": "NETWORK", "availabilityImpact": "NONE", "baseScore": 5.3, "baseSeverity": "MEDIUM", "confidentialityImpact": "HIGH", "integrityImpact": "NONE", "privilegesRequired": "LOW", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N", "version": "3.1"}, "exploitabilityScore": 1.6, "impactScore": 3.6, "source": "[email protected]", "type": "Secondary"}, {"cvssData": {"attackComplexity": "LOW", "attackVector": "NETWORK", "availabilityImpact": "NONE", "baseScore": 6.5, "baseSeverity": "MEDIUM", "confidentialityImpact": "HIGH", "integrityImpact": "NONE", "privilegesRequired": "LOW", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N", "version": "3.1"}, "exploitabilityScore": 2.8, "impactScore": 3.6, "source": "[email protected]", "type": "Primary"}]}, "published": "2021-07-12T23:15:07.807", "references": [{"source": "[email protected]", "tags": ["Release Notes", "Third Party Advisory"], "url": "https://github.com/Icinga/icingaweb2/releases/tag/v2.7.5"}, {"source": "[email protected]", "tags": ["Release Notes", "Third Party Advisory"], "url": "https://github.com/Icinga/icingaweb2/releases/tag/v2.8.3"}, {"source": "[email protected]", "tags": ["Release Notes", "Third Party Advisory"], "url": "https://github.com/Icinga/icingaweb2/releases/tag/v2.9.0"}, {"source": "[email protected]", "tags": ["Exploit", "Third Party Advisory"], "url": "https://github.com/Icinga/icingaweb2/security/advisories/GHSA-2xv9-886q-p7xx"}, {"source": "af854a3a-2127-422b-91ae-364da2661108", "tags": ["Release Notes", "Third Party Advisory"], "url": "https://github.com/Icinga/icingaweb2/releases/tag/v2.7.5"}, {"source": "af854a3a-2127-422b-91ae-364da2661108", "tags": ["Release Notes", "Third Party Advisory"], "url": "https://github.com/Icinga/icingaweb2/releases/tag/v2.8.3"}, {"source": "af854a3a-2127-422b-91ae-364da2661108", "tags": ["Release Notes", "Third Party Advisory"], "url": "https://github.com/Icinga/icingaweb2/releases/tag/v2.9.0"}, {"source": "af854a3a-2127-422b-91ae-364da2661108", "tags": ["Exploit", "Third Party Advisory"], "url": "https://github.com/Icinga/icingaweb2/security/advisories/GHSA-2xv9-886q-p7xx"}], "sourceIdentifier": "[email protected]", "vulnStatus": "Modified", "weaknesses": [{"description": [{"lang": "en", "value": "CWE-200"}], "source": "[email protected]", "type": "Secondary"}, {"description": [{"lang": "en", "value": "CWE-200"}], "source": "[email protected]", "type": "Primary"}]}

{}