# CVE-2019-10979: Hardcoded credentials in MSC800

> Attackers can use hard-coded customer account passwords to gain unauthorized access to SICK MSC800 devices.

- **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:** 1 Jul 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-m5v2-9qv5-hvh2

## What is CVE-2019-10979?

CVE-2019-10979 is a critical vulnerability in SICK MSC800, published on 1 Jul 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SICK MSC800 all versions prior to Version 4.0, the affected firmware versions contain a hard-coded customer account password.

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

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

It affects 1 product.


Products: Sick Msc800 Firmware.

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

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

## Is CVE-2019-10979 being exploited?

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

## Other vulnerabilities in SICK MSC800

- [CVE-2022-27577](https://insights.sbomify.com/CVE-2022-27577/): Other in SICK MSC800 (critical 9.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-10979 is a critical vulnerability in SICK MSC800, published on 1 Jul 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-10979 in the wild and no public exploit code.

Affected product: SICK MSC800. 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-10979/ (Markdown: https://insights.sbomify.com/CVE-2019-10979/index.md)
```

## Sources

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

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