# CVE-2021-32743: Passwords used to access external services inadvertently exposed through API

> Authenticated API users can read database and service passwords, allowing impersonation and data manipulation in external systems.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Jul 2021
- **Updated:** 3 Nov 2025
- **Also known as:** DEBIAN-CVE-2021-32743, GHSA-wrpw-pmr8-qgj7, UBUNTU-CVE-2021-32743

## What is CVE-2021-32743?

CVE-2021-32743 is a high-severity vulnerability in Debian Debian Linux, published on 15 Jul 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-202 (Exposure of Sensitive Information Through Data Queries)

## Which versions are affected by CVE-2021-32743?

It affects 2 products.


Products: Debian Debian Linux, Icinga Icinga.

## How do I fix CVE-2021-32743?

Upgrade to a fixed version.

## Is CVE-2021-32743 being exploited?

There is no known exploitation of CVE-2021-32743 in the wild and no public exploit code.

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-32743 and fix it if it is affected.

What it is: CVE-2021-32743 is a high-severity vulnerability in Debian Debian Linux, published on 15 Jul 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-32743 in the wild and no public exploit code.

Affected product: Debian Debian Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2021-32743/ (Markdown: https://insights.sbomify.com/CVE-2021-32743/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-32743
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-32743
- OSV: https://osv.dev/vulnerability/CVE-2021-32743

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-32743/
Summaries are generated and may contain mistakes; the official description above is the record.