# CVE-2019-5106: Hardcoded credentials in WAGO e!Cockpit

> An attacker can recover user passwords in plain text due to a hard-coded encryption key in WAGO e!Cockpit authentication.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Mar 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-f98g-j2jx-44x5

## What is CVE-2019-5106?

CVE-2019-5106 is a medium-severity vulnerability in WAGO e!Cockpit, published on 10 Mar 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A hard-coded encryption key vulnerability exists in the authentication functionality of WAGO e!Cockpit version 1.5.1.1. An attacker with access to communications between e!Cockpit and CoDeSyS Gateway can trivially recover the password of any user attempting to log in, in plain text.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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

It affects 1 product.


Products: Wago E\!cockpit.

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

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

## Is CVE-2019-5106 being exploited?

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

## Other vulnerabilities in WAGO e!Cockpit

- [CVE-2019-5158](https://insights.sbomify.com/CVE-2019-5158/): Security feature bypass in WAGO e!COCKPIT (high 7.8)
- [CVE-2019-5159](https://insights.sbomify.com/CVE-2019-5159/): Path traversal in WAGO e!COCKPIT (high 7.8)
- [CVE-2019-5107](https://insights.sbomify.com/CVE-2019-5107/): Information disclosure in WAGO e!Cockpit (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-5106 is a medium-severity vulnerability in WAGO e!Cockpit, published on 10 Mar 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-5106 in the wild and no public exploit code.

Affected product: WAGO e!Cockpit. 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-5106/ (Markdown: https://insights.sbomify.com/CVE-2019-5106/index.md)
```

## Sources

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

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