CVE-2019-16674
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn 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. Authentication Information used in a cookie is predictable and can lead to admin password compromise when captured on the network.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceWeidmueller industrial Ethernet switches (IE-SW-VL05M, IE-SW-VL08MT, IE-SW-PL10M) use predictable authentication tokens in cookies. An attacker who captures authentication cookies from network traffic can predict valid session tokens and replay them to gain unauthorized admin access, compromising plaintext passwords.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 3.3.4<= 3.3.4<= 3.4.4<= 3.4.4<= 3.4.4<= 3.4.4<= 3.4.4<= 3.4.4CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the Weidmueller switch modelAccess the device web interface and navigate to System Information or Status page, or check the physical device labelAffected if The model matches any of the following: IE-SW-PL09M 5GC 4GT, IE-SW-PL09MT 5GC 4GT, IE-SW-PL18M 2GC 16TX, IE-SW-PL18MT 2GC 16TX, IE-SW-PL18M 2GC14TX2SC, IE-SW-PL18MT 2GC14TX2SC, IE-SW-PL18M 2GC14TX2ST, or IE-SW-PL18MT 2GC14TX2ST
-
Check the installed firmware versionIn the device web interface, go to System > Firmware or System Information to view the firmware versionAffected if The firmware version is 3.3.4 or lower for PL09M/PL09MT models, or 3.4.4 or lower for PL18M/PL18MT models
-
Confirm network accessibility of management interfaceAttempt to access the device web interface from an untrusted network or verify the HTTP/HTTPS service is listening on interfaces accessible to usersAffected if The management web interface is reachable from networks outside the local administrative segment
The device is affected if it is one of the listed Weidmueller switch models with firmware at or below the specified version AND the web management interface with cookie-based authentication is accessible.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate firmware from Weidmueller when available; meanwhile, isolate affected devices on a restricted network segment, enforce TLS for all management traffic, and monitor for anomalous authentication patterns.
- Consultation8.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,608.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-16674 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-16674 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data