Security readout for executives and security teams
Plain-English summary
CVE-2021-32739 lets a low-privileged, authenticated Icinga API user see sensitive certificate-ticket material. That can allow identity theft inside Icinga, including impersonating more privileged API users or endpoints. This is a high-priority monitoring-platform issue because compromise could affect confidentiality, integrity, and availability of monitored infrastructure operations.
Executive priority
Treat as high priority for any affected Icinga deployment. A low-privileged API account could become a path to trusted identity impersonation in the monitoring system, which can undermine operational visibility and control.
Technical view
Icinga 2 versions 2.4.0 through 2.12.4 expose ApiListener ticket_salt through config object queries to authenticated API users. The salt can be used to derive certificate tickets for common names, enabling unauthorized certificate issuance and subsequent endpoint or API identity impersonation. Fixed releases are 2.12.5 and 2.11.10.
Likely exposure
Exposure is likely where Icinga 2.4.0 through 2.12.4 is deployed with API access granted to read-only or other low-privileged users. Risk is highest when API users can query broad config object attributes, including ApiListener objects.
Exploitation context
The sources describe authenticated privilege escalation but do not cite active exploitation. The CVE is not marked KEV in the provided bundle. Exploitation requires valid API credentials and access to query exposed configuration attributes.
Researcher notes
The core issue is improper privilege handling around sensitive ApiListener ticket_salt exposure. Evidence supports authenticated escalation, not unauthenticated access. The bundle names affected versions, fixed versions, and two workarounds, but does not provide confirmed exploitation evidence.
Mitigation direction
- Upgrade Icinga 2 to 2.12.5, 2.11.10, or a later fixed release.
- Apply the documented workaround by explicitly limiting queryable types.
- Alternatively, filter ApiListener objects from API query results.
- Review API accounts and remove unnecessary read access.
- Check vendor and distribution advisories for package-specific update guidance.
Validation and detection
- Inventory Icinga 2 versions and flag 2.4.0 through 2.12.4.
- Confirm installed packages include the fixed vendor or distribution release.
- Review API permissions for broad config object query access.
- Verify ApiListener objects are excluded or queryable types are explicitly restricted.
- Assess whether suspicious certificate or API identity activity requires incident response.
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-267: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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 lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2021-32739 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
- High
- CVSS
- 8.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.8HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/Icinga/icinga2/security/advisories/GHSA-98wp-jc6q-x5q5CVE reference · x_refsource_CONFIRM
- https://icinga.com/blog/2021/07/02/releasing-icinga-2-12-5-2-11-10/CVE reference · x_refsource_MISC
- [debian-lts-announce] 20211110 [SECURITY] [DLA 2816-1] icinga2 security updateCVE reference · mailing-list, x_refsource_MLIST
- https://lists.debian.org/debian-lts-announce/2024/11/msg00010.htmlCVE reference
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.
Privilege Defined With Unsafe Actions
Privilege Defined With Unsafe Actions represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.