# CVE-2021-34577: Hardcoded credentials in Kaden PICOFLUX AiR

> An attacker with physical proximity can read water meter data using a hardcoded key in wireless M-Bus mode.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Nov 2022
- **Updated:** 1 May 2025
- **Also known as:** GHSA-q3wx-xp39-27ph

## What is CVE-2021-34577?

CVE-2021-34577 is a medium-severity vulnerability in Kaden PICOFLUX AiR, published on 9 Nov 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Kaden PICOFLUX AiR water meter an adversary can read the values through wireless M-Bus mode 5 with a hardcoded shared key while being adjacent to the device.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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

It affects 1 product.


Products: Kadenvodomery Picoflux Air Firmware.

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

No fix has been published for CVE-2021-34577 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-34577 being exploited?

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

## Other vulnerabilities in Kaden PICOFLUX AiR

- [CVE-2021-34576](https://insights.sbomify.com/CVE-2021-34576/): Observable discrepancy in Kaden PICOFLUX AiR leaks water consumption (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-34577 is a medium-severity vulnerability in Kaden PICOFLUX AiR, published on 9 Nov 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-34577 in the wild and no public exploit code.

Affected product: Kaden PICOFLUX AiR. 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-34577/ (Markdown: https://insights.sbomify.com/CVE-2021-34577/index.md)
```

## Sources

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

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