CVE-2021-32743: Passwords used to access external services inadvertently exposed through API
Noroxi assessment
Priority: Monitor (action score 36/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.8% (FIRST EPSS); higher than 78.8% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: icinga2 (Debian:11) 2.12.3-1+deb11u1; icinga2 (Debian:12) 2.12.5-1; icinga2 (Debian:9) 2.6.0-2+deb9u2.
Low priority for now. Upgrade to icinga2 (Debian:11) 2.12.3-1+deb11u1; icinga2 (Debian:12) 2.12.5-1; icinga2 (Debian:9) 2.6.0-2+deb9u2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Icinga is a monitoring system which checks the availability of network resources, notifies users of outages, and generates performance data for reporting. In versions prior to 2.11.10 and from version 2.12.0 through version 2.12.4, some of the Icinga 2 features that require credentials for external services expose those credentials through the API to authenticated API users with read permissions for the corresponding object types. IdoMysqlConnection and IdoPgsqlConnection (every released version) exposes the password of the user used to connect to the database. IcingaDB (added in 2.12.0) exposes the password used to connect to the Redis server. ElasticsearchWriter (added in 2.8.0)exposes the password used to connect to the Elasticsearch server. An attacker who obtains these credentials can impersonate Icinga to these services and add, modify and delete information there. If credentials with more permissions are in use, this increases the impact accordingly. Starting with the 2.11.10 and 2.12.5 releases, these passwords are no longer exposed via the API. As a workaround, API user permissions can be restricted to not allow querying of any affected objects, either by explicitly listing only the required object types for object query permissions, or by applying a filter rule.
- Published
- Jul 15, 2021
- Updated
- Jun 16, 2026
- EPSS
- 1.8% · 78th percentile
- CWE
- CWE-202
Report tools
Action score
36
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 1.8%
CNA vs NVD score
- NVD
- 8.8
- CNA · GitHub_M
- 8.8
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
Icinga icinga2
- < 2.11.10, >= 2.12.0, <= 2.12.4affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux9.0
- icinga icinga2.0.0 and later · before 2.11.10
- icinga icinga2.12.0 and later · before 2.12.5
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:11 | icinga2 | before 2.12.3-1+deb11u1 | 2.12.3-1+deb11u1 |
| Debian:12 | icinga2 | before 2.12.5-1 | 2.12.5-1 |
| Debian:9 | icinga2 | before 2.6.0-2+deb9u2 | 2.6.0-2+deb9u2 |
| openSUSE:Leap 15.2 | icinga2 | before 2.12.5-bp153.2.5.1 | 2.12.5-bp153.2.5.1 |
| openSUSE:Tumbleweed | icinga2 | before 2.13.1-1.3 | 2.13.1-1.3 |
| SUSE:Package Hub 15 SP1 | icinga2 | before 2.12.5-bp153.2.5.1 | 2.12.5-bp153.2.5.1 |
Same product
icinga: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-49369Icinga 2 has a TLS Certificate Validation Bypass for JSON-RPC and HTTP API Connections40Plan
- CVE-2025-48057Icinga 2 certificate renewal might incorrectly renew an invalid certificate37Monitor
- CVE-2020-29663Icinga 2 v2.8.0 through v2.11.7 and v2.12.2 has an issue where revoked certificates due for renewal will automatically be renewed, ignoring…36Monitor
Published before and after this one in the same product
- ← EarlierCVE-2021-32747Jul 12, 2021 · Custom variable protection and blacklists can be circumvented26Monitor
- ← EarlierCVE-2021-32739Jul 15, 2021 · Results of queries for ApiListener objects include the ticket salt which allows in turn to steal (more privileged) identities35Monitor
- Later →CVE-2021-37698Aug 19, 2021 · Missing TLS service certificate validation in GelfWriter, ElasticsearchWriter, InfluxdbWriter and Influxdb2Writer30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:icinga2 | 2.12.5-1 · Debian:12 | Package registry (OSV) |
| opensuse:icinga2 | 2.12.5-bp153.2.5.1 · openSUSE:Leap 15.2 | Package registry (OSV) |
| suse:icinga2 | 2.12.5-bp153.2.5.1 · SUSE:Package Hub 15 SP1 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-202 · Exposure of Sensitive Information Through Data QueriesCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.