Security readout for executives and security teams
Plain-English summary
CVE-2021-32747 can expose sensitive Icinga custom variables to logged-in users who should not see them. These variables may contain secrets used by monitoring checks. The issue is not listed as known exploited, but disclosure of service credentials can create downstream business risk if those secrets are reused or privileged.
Executive priority
Treat this as a moderate-priority confidentiality issue. Patch during the next security maintenance window, faster if Icinga custom variables contain production credentials or broad-access tokens. The main business concern is secondary compromise from exposed secrets, not direct system takeover through this CVE alone.
Technical view
Icinga Web 2 versions 2.0.0 through 2.8.2 improperly enforce custom variable protection rules and blacklists on certain list and export views. An undocumented URL parameter can cause additional custom variable columns to be returned, including JSON or CSV output, with protected values shown as-is.
Likely exposure
Exposure is limited to Icinga Web 2 deployments in the affected version range where authenticated users can access hosts or services containing sensitive custom variables. Risk increases when custom variables store credentials, tokens, or other secrets and role protections or blacklists are relied on for confidentiality.
Exploitation context
The source bundle does not show CISA KEV listing or evidence of active exploitation. Exploitation requires a logged-in user with access to affected hosts or services and knowledge of the alternate access path. Impact is confidentiality only, but leaked monitoring secrets may enable further compromise outside Icinga.
Researcher notes
The available evidence supports affected versions, confidentiality impact, and fixed releases. It does not prove public exploitation. Validation should focus on version state, role-scoped exposure to host and service custom variables, export behavior, and whether sensitive values were stored in those variables.
Mitigation direction
- Upgrade Icinga Web 2 to 2.9.0, 2.8.3, 2.7.5, or a later supported release.
- If immediate upgrade is unavailable, restrict visibility of hosts and services containing sensitive custom variables.
- Review custom variables and remove secrets where operationally possible.
- Rotate any secrets that may have been exposed to lower-privileged users.
- Reassess role protection rules and blacklists after upgrading.
Validation and detection
- Inventory Icinga Web 2 versions and flag 2.0.0 through 2.8.2.
- Identify roles and users with host or service access where custom variables may contain secrets.
- Verify exports and list views no longer reveal protected or blacklisted custom variables after remediation.
- Check application logs for suspicious access to list or export routes if logging is available.
- Confirm any potentially exposed secrets were rotated or otherwise invalidated.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-200: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2021-32747 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N1.63.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.3MediumVector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/Icinga/icingaweb2/releases/tag/v2.7.5CVE reference · x_refsource_MISC
- https://github.com/Icinga/icingaweb2/releases/tag/v2.8.3CVE reference · x_refsource_MISC
- https://github.com/Icinga/icingaweb2/releases/tag/v2.9.0CVE reference · x_refsource_MISC
- https://github.com/Icinga/icingaweb2/security/advisories/GHSA-2xv9-886q-p7xxCVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Exposure of Sensitive Information to an Unauthorized Actor
Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.