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.

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - 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. (CVE-2021-32747)

Note that Nessus relies on the presence of the package as reported by the vendor.

There are packages installed that are affected by multiple vulnerabilities referenced in the following CVEs:

  - Icinga Web 2 is an open source monitoring web interface, framework and command-line interface. Between
    versions 2.3.0 and 2.8.2, the `doc` module of Icinga Web 2 allows to view documentation directly in the
    UI. It must be enabled manually by an administrator and users need explicit access permission to use it.
    Then, by visiting a certain route, it is possible to gain access to arbitrary files readable by the web-
    server user. The issue has been fixed in the 2.9.0, 2.8.3, and 2.7.5 releases. As a workaround, an
    administrator may disable the `doc` module or revoke permission to use it from all users. (CVE-2021-32746)

  - 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. (CVE-2021-32747)

ID	Name	Product	Family	Severity
223783	Linux Distros Unpatched Vulnerability : CVE-2021-32747	Nessus	Misc.	medium
404925	Alpine: multiple icingaweb2 packages: security update to 2.9.0-r0	Tenable Cloud Security	Alpine Linux Local Security Checks	medium
404925	Alpine: multiple icingaweb2 packages: security update to 2.9.0-r0	Tenable Self-Hosted Container Security	Alpine Linux Local Security Checks	medium
400192	Alpine: multiple icingaweb2 packages: security update to 2.8.2-r0 (deprecated)	Tenable Cloud Security	Alpine Linux Local Security Checks	medium
400192	Alpine: multiple icingaweb2 packages: security update to 2.8.2-r0 (deprecated)	Tenable Self-Hosted Container Security	Alpine Linux Local Security Checks	medium

Detections

Analytics

CVE-2021-32747

medium

Tenable Plugins

medium

medium

medium

medium

medium