# CVE-2019-16670: Security feature bypass in n/a

> Attackers can brute-force credentials on Weidmueller industrial switches due to missing rate limiting, potentially gaining administrative access.

- **Severity:** Critical 9.8 (`CVSS:3.0/AC:L/AV:N/A:H/C:H/I:H/PR:N/S:U/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Dec 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-858h-9hh5-fvx2

## What is CVE-2019-16670?

CVE-2019-16670 is a critical vulnerability in n/a, published on 6 Dec 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 Weidmueller IE-SW-VL05M 3.6.6 Build 16102415, IE-SW-VL08MT 3.5.2 Build 16102415, and IE-SW-PL10M 3.3.16 Build 16102416 devices. The Authentication mechanism has no brute-force prevention.

Weakness: CWE-307 (Improper Restriction of Excessive Authentication Attempts)

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

It affects 40 products.


Products: Weidmueller Ie-Sw-Pl08m-6tx-2sc Firmware, Weidmueller Ie-Sw-Pl08m-6tx-2scs Firmware, Weidmueller Ie-Sw-Pl08m-6tx-2st Firmware, Weidmueller Ie-Sw-Pl08m-8tx Firmware, Weidmueller Ie-Sw-Pl08mt-6tx-2sc Firmware, Weidmueller Ie-Sw-Pl08mt-6tx-2scs Firmware, Weidmueller Ie-Sw-Pl08mt-6tx-2st Firmware, Weidmueller Ie-Sw-Pl08mt-8tx Firmware, Weidmueller Ie-Sw-Pl09m-5gc-4gt Firmware, Weidmueller Ie-Sw-Pl09mt-5gc-4gt Firmware, Weidmueller Ie-Sw-Pl10m-1gt-2gs-7tx Firmware, Weidmueller Ie-Sw-Pl10m-3gt-7tx Firmware, Weidmueller Ie-Sw-Pl10mt-1gt-2gs-7tx Firmware, Weidmueller Ie-Sw-Pl10mt-3gt-7tx Firmware, Weidmueller Ie-Sw-Pl16m-14tx-2sc Firmware, Weidmueller Ie-Sw-Pl16m-14tx-2st Firmware, Weidmueller Ie-Sw-Pl16m-16tx Firmware, Weidmueller Ie-Sw-Pl16mt-14tx-2sc Firmware, Weidmueller Ie-Sw-Pl16mt-14tx-2st Firmware, Weidmueller Ie-Sw-Pl16mt-16tx Firmware and 20 more.

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

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

## Is CVE-2019-16670 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-16672](https://insights.sbomify.com/CVE-2019-16672/): Information disclosure in n/a (critical 9.8)
- [CVE-2019-16674](https://insights.sbomify.com/CVE-2019-16674/): Weak cryptography in n/a (critical 9.8)
- [CVE-2019-16673](https://insights.sbomify.com/CVE-2019-16673/): Information disclosure in n/a (high 7.5)
- [CVE-2019-16671](https://insights.sbomify.com/CVE-2019-16671/): Denial of service in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-16670 is a critical vulnerability in n/a, published on 6 Dec 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-16670 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-16670/ (Markdown: https://insights.sbomify.com/CVE-2019-16670/index.md)
```

## Sources

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

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