# CVE-2019-20481: Auth bypass in n/a

> Attackers can change passwords without knowing the old one, leading to account takeover on Miele ZigBee Gateways.

- **Severity:** Medium 4.6 (`CVSS:3.0/AC:H/AV:N/A:L/C:L/I:L/PR:L/S:U/UI:R`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 24 Feb 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-m4qw-fm6j-8h62

## What is CVE-2019-20481?

CVE-2019-20481 is a medium-severity authentication bypass vulnerability in n/a, published on 24 Feb 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

In MIELE XGW 3000 ZigBee Gateway before 2.4.0, the Password Change Function does not require knowledge of the old password. This can be exploited in conjunction with CVE-2019-20480.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2019-20481?

It affects 1 product.


Products: Miele Xgw 3000 Zigbee Gateway Firmware.

## How do I fix CVE-2019-20481?

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

## Is CVE-2019-20481 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-20480](https://insights.sbomify.com/CVE-2019-20480/): Cross-site request forgery in n/a (medium 4.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-20481 and fix it if it is affected.

What it is: CVE-2019-20481 is a medium-severity authentication bypass vulnerability in n/a, published on 24 Feb 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-20481 in the wild and no public exploit code.

Affected product: n/a. 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-2019-20481/ (Markdown: https://insights.sbomify.com/CVE-2019-20481/index.md)
```

## Sources

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

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