# CVE-2019-17216: Weak cryptography in n/a

> Attackers can crack MD5-hashed passwords on V-Zug Combi-Steam devices to gain unauthorized access.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 6 Oct 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-jq2w-xm8x-j998

## What is CVE-2019-17216?

CVE-2019-17216 is a critical vulnerability in n/a, published on 6 Oct 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered on V-Zug Combi-Steam MSLQ devices before Ethernet R07 and before WLAN R05. Password authentication uses MD5 to hash passwords. Cracking is possible with minimal effort.

Weakness: CWE-916 (Use of Password Hash With Insufficient Computational Effort)

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

It affects 1 product.


Products: Vzug Combi-Stream Mslq Firmware.

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

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

## Is CVE-2019-17216 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-17215](https://insights.sbomify.com/CVE-2019-17215/): Security feature bypass in n/a (critical 9.8)
- [CVE-2019-17218](https://insights.sbomify.com/CVE-2019-17218/): Information disclosure in n/a (critical 9.1)
- [CVE-2019-17217](https://insights.sbomify.com/CVE-2019-17217/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2019-17219](https://insights.sbomify.com/CVE-2019-17219/): Missing authorization in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-17216 is a critical vulnerability in n/a, published on 6 Oct 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-17216 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-17216/ (Markdown: https://insights.sbomify.com/CVE-2019-17216/index.md)
```

## Sources

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

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