# CVE-2019-6578: Denial of service in SINAMICS PERFECT HARMONY GH180 with NXG I control, MLFBs: 6SR2...-, 6SR3...-, 6SR4...-

> An unauthenticated remote attacker can cause a denial of service on Siemens SINAMICS PERFECT HARMONY GH180 drives via network access.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:** 14 May 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-qj25-jwcw-gvf6

## What is CVE-2019-6578?

CVE-2019-6578 is a high-severity denial of service vulnerability in Siemens AG SINAMICS PERFECT HARMONY GH180 with NXG I control, MLFBs: 6SR2...-, 6SR3...-, 6SR4...-, published on 14 May 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability has been identified in SINAMICS PERFECT HARMONY GH180 with NXG I control, MLFBs: 6SR2...-, 6SR3...-, 6SR4...- (All Versions with option G28), SINAMICS PERFECT HARMONY GH180 with NXG II control, MLFBs: 6SR2...-, 6SR3...-, 6SR4...- (All Versions with option G28). A denial of service vulnerability exists in the affected products. The vulnerability could be exploited by an attacker with network access to the device. Successful exploitation requires no privileges and no user interaction. An attacker could use the vulnerability to compromise availability of the affected system. At the time of advisory publication no public exploitation of this security vulnerability was known.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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

It affects 6 products.


Products: Siemens Sinamics Perfect Harmony Gh180 With Nxg I Control Mlfb 6sr2 Firmware, Siemens Sinamics Perfect Harmony Gh180 With Nxg I Control Mlfb 6sr3 Firmware, Siemens Sinamics Perfect Harmony Gh180 With Nxg I Control Mlfb 6sr4 Firmware, Siemens Sinamics Perfect Harmony Gh180 With Nxg Ii Control Mlfb 6sr2 Firmware, Siemens Sinamics Perfect Harmony Gh180 With Nxg Ii Control Mlfb 6sr3 Firmware, Siemens Sinamics Perfect Harmony Gh180 With Nxg Ii Control Mlfb 6sr4 Firmware.

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

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

## Is CVE-2019-6578 being exploited?

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

## Other vulnerabilities in Siemens AG SINAMICS PERFECT HARMONY GH180 with NXG I control, MLFBs: 6SR2...-, 6SR3...-, 6SR4...-

- [CVE-2019-6574](https://insights.sbomify.com/CVE-2019-6574/): Denial of service in SINAMICS PERFECT HARMONY GH180 with NXG I control, MLFBs: 6SR2...-, 6SR3...-, 6SR4...- (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-6578 is a high-severity denial of service vulnerability in Siemens AG SINAMICS PERFECT HARMONY GH180 with NXG I control, MLFBs: 6SR2...-, 6SR3...-, 6SR4...-, published on 14 May 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-6578 in the wild and no public exploit code.

Affected product: Siemens AG SINAMICS PERFECT HARMONY GH180 with NXG I control, MLFBs: 6SR2...-, 6SR3...-, 6SR4...-. 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-6578/ (Markdown: https://insights.sbomify.com/CVE-2019-6578/index.md)
```

## Sources

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

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