CVE-2019-5107
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 · uneditedA cleartext transmission vulnerability exists in the network communication functionality of WAGO e!Cockpit version 1.5.1.1. An attacker with access to network traffic can easily intercept, interpret, and manipulate data coming from, or destined for e!Cockpit. This includes passwords, configurations, and binaries being transferred to endpoints.
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 · high confidenceWAGO e!Cockpit version 1.5.1.1 transmits all network communications in cleartext without encryption. An attacker with network access can intercept, read, and manipulate sensitive data including passwords, configurations, and binaries being transferred between the application and endpoints.
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= 1.5.1.1CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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.
-
Verify WAGO e!Cockpit installationLocate the e!Cockpit application on the system. Check standard installation directories or use system tools to list installed software packages named 'e!Cockpit' or 'WAGO'.Affected if WAGO e!Cockpit software is present on the system
-
Determine installed e!Cockpit versionAccess the application's 'About' or 'Help' section, or check the Windows Programs and Features list, or examine the executable file properties for version information. Compare the version number to 1.5.1.1.Affected if The installed version is exactly 1.5.1.1
-
Inspect network configuration for encryptionExamine the application's configuration files or network settings to determine whether TLS/SSL encryption is enabled for network communications. Look for options related to 'Encrypted Connection', 'SSL', 'TLS', or 'HTTPS' in the settings.Affected if TLS/SSL encryption is disabled or not configured, and the version is 1.5.1.1
-
Monitor network traffic from e!CockpitUse a network packet capture tool (such as Wireshark) to capture traffic while e!Cockpit communicates with endpoints. Verify whether traffic is transmitted in plaintext (no TLS/SSL wrapper).Affected if Network packets show unencrypted plaintext communication and the version is 1.5.1.1
A user is affected if WAGO e!Cockpit version 1.5.1.1 is installed and network communications are transmitted in cleartext without TLS/SSL encryption.
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 dataImplement TLS/SSL encryption for all network communications in e!Cockpit, or use VPN tunneling to protect data in transit. Additionally, enforce HTTPS for all web-based interfaces and validate SSL certificates to prevent man-in-the-middle attacks.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-5107 — 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-5107 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