dbcve.org
E\!cockpitApplication · Wago

CVE-2019-5158

HIGH · 7.8 CVSS v3.1 Published 2020-03-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
No privileges

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 · unedited
An exploitable firmware downgrade vulnerability exists in the firmware update package functionality of the WAGO e!COCKPIT automation software v1.6.1.5. A specially crafted firmware update file can allow an attacker to install an older firmware version while the user thinks a newer firmware version is being installed. An attacker can create a custom firmware update package with invalid metadata in order to trigger this vulnerability.

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 confidence

The WAGO e!COCKPIT automation software v1.6.1.5 has a firmware downgrade vulnerability in its firmware update package functionality. Attackers can craft custom firmware update packages with invalid metadata that trick users into installing older firmware versions while believing they are installing newer ones. This bypasses the intended version validation in the firmware update process.

MitigationApply vendor patch for WAGO e!COCKPIT to include proper cryptographic validation of firmware metadata and enforce that only strictly newer firmware versions can be installed. Until patched, verify firmware integrity through alternative means before deployment.

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
E\!cockpitApplication
Affected:= 1.6.1.5

CVSS 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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed WAGO e!COCKPIT version
    Locate and inspect the installed e!COCKPIT software version through the application itself (typically via Help > About or the software's version information), or check the program's uninstall/change information in the system control panel
    Affected if The installed version is exactly 1.6.1.5 (the only affected version listed)
  2. Determine if firmware update functionality is in use
    Check whether the e!COCKPIT firmware update package feature has been configured or used on this system. Look for any firmware update-related configuration files, logs, or recent firmware deployment activities within the software
    Affected if Firmware update functionality is actively used or configured on the system
  3. Review firmware package sources
    Examine any firmware update packages present on the system or network for signs of custom or third-party origin. Verify that all firmware packages were obtained from official WAGO distribution channels only
    Affected if Any firmware packages originate from unofficial, custom, or third-party sources rather than official WAGO channels
  4. Inspect firmware metadata for version anomalies
    If firmware packages are available, examine the metadata (version information, timestamps, signatures) within the packages to identify any inconsistencies that suggest version manipulation or downgrade metadata
    Affected if Firmware packages contain invalid or inconsistent metadata that does not match expected values for the claimed version

A system is affected if WAGO e!COCKPIT version 1.6.1.5 is installed AND the firmware update feature is being used, particularly with packages from non-official sources or showing metadata inconsistencies.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patch for WAGO e!COCKPIT to include proper cryptographic validation of firmware metadata and enforce that only strictly newer firmware versions can be installed. Until patched, verify firmware integrity through alternative means before deployment.

Fix this in E\!cockpit Scoped from the published advisory
  • Consultation3.0 h
  • Implementation10.0 h
  • Testing5.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,690
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,904.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-5158 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-5158 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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