# CVE-2022-27577: Other in SICK MSC800

> Attackers can predict TCP sequence numbers to forge packets and compromise services on the SICK MSC800 industrial device.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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:** 11 Apr 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-crjp-2pp7-rchg

## What is CVE-2022-27577?

CVE-2022-27577 is a critical vulnerability in SICK MSC800, published on 11 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The vulnerability in the MSC800 in all versions before 4.15 allows for an attacker to predict the TCP initial sequence number. When the TCP sequence is predictable, an attacker can send packets that are forged to appear to come from a trusted computer. These forged packets could compromise services on the MSC800. SICK has released a new firmware version of the SICK MSC800 and recommends updating to the newest version.

Weakness: CWE-330 (Use of Insufficiently Random Values), CWE-342 (Predictable Exact Value from Previous Values)

## Which versions are affected by CVE-2022-27577?

It affects 1 product.


Products: Sick Msc800 Firmware.

## How do I fix CVE-2022-27577?

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

## Is CVE-2022-27577 being exploited?

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

## Other vulnerabilities in SICK MSC800

- [CVE-2019-10979](https://insights.sbomify.com/CVE-2019-10979/): Hardcoded credentials in MSC800 (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-27577 and fix it if it is affected.

What it is: CVE-2022-27577 is a critical vulnerability in SICK MSC800, published on 11 Apr 2022. 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-2022-27577 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-2022-27577/ (Markdown: https://insights.sbomify.com/CVE-2022-27577/index.md)
```

## Sources

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

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