# CVE-2019-12549: Hardcoded credentials in n/a

> Hardcoded SSH private keys in WAGO industrial controllers allow attackers to bypass authentication and potentially execute code.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jun 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-fg4f-r3w9-j9pg

## What is CVE-2019-12549?

CVE-2019-12549 is a critical vulnerability in n/a, published on 17 Jun 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

WAGO 852-303 before FW06, 852-1305 before FW06, and 852-1505 before FW03 devices contain hardcoded private keys for the SSH daemon. The fingerprint of the SSH host key from the corresponding SSH daemon matches the embedded private key.

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

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

It affects 3 products.


Products: Wago 852-1305 Firmware, Wago 852-1505 Firmware, Wago 852-303 Firmware.

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

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

## Is CVE-2019-12549 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-12550](https://insights.sbomify.com/CVE-2019-12550/): Hardcoded credentials in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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