CVE-2022-27577
First published: Mon Apr 11 2022(Updated: )
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.
Credit: psirt@sick.de
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Sick Msc800 Firmware | <4.15 | |
| SICK MSC800 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the vulnerability ID for this vulnerability?
The vulnerability ID for this vulnerability is CVE-2022-27577.
What is the severity of CVE-2022-27577?
The severity of CVE-2022-27577 is critical with a severity value of 9.1.
What is the affected software for CVE-2022-27577?
The affected software for CVE-2022-27577 is Sick Msc800 Firmware versions up to exclusive 4.15.
What is the CWE ID of CVE-2022-27577?
The CWE ID of CVE-2022-27577 is CWE-330 and CWE-342.
How can an attacker exploit CVE-2022-27577?
An attacker can exploit CVE-2022-27577 by predicting the TCP initial sequence number and sending forged packets that appear to come from a trusted computer.
- collector/nvd-index
- agent/references
- agent/weakness
- agent/severity
- agent/author
- agent/type
- agent/tags
- agent/event
- agent/description
- agent/last-modified-date
- agent/softwarecombine
- agent/first-publish-date
- collector/mitre-cve
- source/MITRE
- vendor/sick
- canonical/sick msc800 firmware
- canonical/sick msc800