# CVE-2021-23846: B426 Credential Disclosure

> Attackers can intercept user passwords transmitted in clear text over HTTP via MITM attacks on Bosch B426 devices.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 18 Jun 2021
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-6g22-rpp3-9gm7

## What is CVE-2021-23846?

CVE-2021-23846 is a high-severity vulnerability in Bosch B426 Firmware, published on 18 Jun 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

When using http protocol, the user password is transmitted as a clear text parameter for which it is possible to be obtained by an attacker through a MITM attack. This will be fixed starting from Firmware version 3.11.5, which will be released on the 30th of June, 2021.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

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

It affects 1 product.


Products: Bosch B426 Firmware.

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

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

## Is CVE-2021-23846 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-23846 is a high-severity vulnerability in Bosch B426 Firmware, published on 18 Jun 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2021-23846 in the wild and no public exploit code.

Affected product: Bosch B426 Firmware. 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-23846/ (Markdown: https://insights.sbomify.com/CVE-2021-23846/index.md)
```

## Sources

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

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