SICK vulnerabilities
We track 83 vulnerabilities in SICK products across 60+ products. 83 are rated high or critical, and none are known to be exploited. The most recent was published on October 15, 2026.
Latest SICK vulnerabilities
- 7.5 High severity
Sick_Safetyscanners_Base CPP Driver: Out-of-bounds Read
A remote attacker may send a specially crafted network packet that causes the affected application to perform an out-of-bounds memory read due to insufficient validation of packet length. This may result in an application crash and a denial-of-service conditio
- 8.3 High severity
Sentio Creator Extension 'Device Manager': Improper Verification of Cryptographic Signature
An attacker may achieve arbitrary code execution on a target system by uploading a malicious device driver package, bypassing driver verification mechanisms, and triggering the execution of attacker-controlled code. User interaction is required.
- 9.4 Critical severity
InspectorP61x: Files or Directories Accessible to External Parties
An attacker may perform unauthenticated read and write operations on sensitive filesystem areas via the AppEngine Fileaccess over HTTP due to improper access restrictions. A critical filesystem directory was unintentionally exposed through the HTTP-based file
- 9.8 Critical severity
SICK Lector85x: Files or Directories Accessible to External Parties
An attacker may perform unauthenticated read and write operations on sensitive filesystem areas via the AppEngine Fileaccess over HTTP due to improper access restrictions. A critical filesystem directory was unintentionally exposed through the HTTP-based file
- 9.4 Critical severity
SICK Lector85x: Files or Directories Accessible to External Parties
An attacker may access restricted filesystem areas on the device via the CROWN REST interface due to incomplete whitelist enforcement. Certain directories intended for internal testing were not covered by the whitelist and are accessible without authentication
- 8.1 High severity
SICK LMS1000: Use of a Broken or Risky Cryptographic Algorithm
An attacker may exploit the use of outdated and weak MAC algorithms in the device’s SSH service to potentially compromise the integrity of the SSH session, allowing manipulation of transmitted data if the attacker can interact with the network traffic.
- 9.1 Critical severity
SICK LMS1000: Use of a Broken or Risky Cryptographic Algorithm
An attacker may exploit the use of weak CBC-based cipher suites in the device’s SSH service to potentially observe or manipulate parts of the encrypted SSH communication, if they are able to intercept or interact with the network traffic.
- 7.5 High severity
Incoming Goods Suite: Generation of Error Message Containing Sensitive Information
Certain error messages returned by the application expose internal system details that should not be visible to end users, providing attackers with valuable reconnaissance information (like file paths, database errors, or software versions) that can be used to
- 7.5 High severity
Incoming Goods Suite: Use of HTTP Request With Sensitive Query String
Certain requests pass the authentication token in the URL as string query parameter, making it vulnerable to theft through server logs, proxy logs and Referer headers, which could allow an attacker to hijack the user's session and gain unauthorized access.
- 8.2 High severity
TDC-X401GL: Improper Restriction of Rendered UI Layers or Frames
An attacker may exploit missing protection against clickjacking by tricking users into performing unintended actions through maliciously crafted web pages, leading to the extraction of sensitive data.
- 7.5 High severity
TDC-X401GL: Insufficiently Protected Credentials
Firmware update files may expose password hashes for system accounts, which could allow a remote attacker to recover credentials and gain unauthorized access to the device.
- 9.1 Critical severity
TDC-X401GL: Use of Weak Credentials
The device is deployed with weak and publicly known default passwords for certain hidden user levels, increasing the risk of unauthorized access. This represents a high risk to the integrity of the system.
- 9.1 Critical severity
TDC-X401GL: Incorrect Authorization
Certain system functions may be accessed without proper authorization, allowing attackers to start, stop, or delete installed applications, potentially disrupting system operations.
- 9.1 Critical severity
TDC-X401GL: Incorrect Privilege Assignment
Uploading unvalidated container images may allow remote attackers to gain full access to the system, potentially compromising its integrity and confidentiality.
- 7.5 High severity
TLOC100-100 with Firmware <7.1.1: Use of Weak Credentials
The system is deployed in its default state, with configuration settings that do not comply with the latest best practices for restricting access. This increases the risk of unauthorised connections.
- 7.5 High severity
TLOC100-100: Allocation of Resources Without Limits or Throttling
An attacker that gains SSH access to an unprivileged account may be able to disrupt services (including SSH), causing persistent loss of availability.
- 7.5 High severity
Baggage Analytics: Authentication Bypass Using an Alternate Path or Channel
The credentials of the users stored in the system's local database can be used for the log in, making it possible for an attacker to gain unauthorized access. This could potentially affect the confidentiality of the application.
- 7.5 High severity
Baggage Analytics: Improper Limitation of a Pathname to a Restricted Directory
A remote, unauthorized attacker can brute force folders and files and read them like private keys or configurations, making the application vulnerable for gathering sensitive information.
- 9.8 Critical severity
Baggage Analytics: Improper Restriction of Excessive Authentication Attempts
The application does not implement sufficient measures to prevent multiple failed authentication attempts within a short time frame, making it possible for an attacker to guess user credentials.
- 7.5 High severity
Baggage Analytics: Use of HTTP Request With Sensitive Query String
In the HTTP request, the username and password are transferred directly in the URL as parameters. However, URLs can be stored in various systems such as server logs, browser histories or proxy servers. As a result, there is a high risk that this sensitive data
- 7.5 High severity
Enterprise Analytics: Allocation of Resources Without Limits or Throttling
If a user tries to login but the provided credentials are incorrect a log is created. The data for this POST requests is not validated and it’s possible to send giant payloads which are then logged.
- 7.5 High severity
SICK Field Analytics: Exposure of Sensitive Information to an Unauthorized Actor
The created backup files are unencrypted, making the application vulnerable for gathering sensitive information by downloading and decompressing the backup files.
- 9.8 Critical severity
SICK Field Analytics: Insufficient Verification of Data Authenticity
The backup ZIPs are not signed by the application, leading to the possibility that an attacker can download a backup ZIP, modify and re-upload it. This allows the attacker to disrupt the application by configuring the services in a way that they are unable to
- 7.5 High severity
SICK Media Server: Use of Insufficiently Random Values
The Media Server’s authorization tokens have a poor quality of randomness. An attacker may be able to guess the token of an active user by computing plausible tokens.
- 9.1 Critical severity
SICK Field Analytics: Use of a Broken or Risky Cryptographic Algorithm
A service supports the use of a deprecated and unsafe TLS version. This could be exploited to expose sensitive information, modify data in unexpected ways or spoof identities of other users or devices, affecting the confidentiality and integrity of the device.
- 9.8 Critical severity
SICK Media Server: Improper Restriction of Excessive Authentication Attempts
The FTP server’s login mechanism does not restrict authentication attempts, allowing an attacker to brute-force user passwords and potentially compromising the FTP server.
- 7.5 High severity
SICK Media Server: Cleartext Transmission of Sensitive Information
The server supports authentication methods in which credentials are sent in plaintext over unencrypted channels. If an attacker were to intercept traffic between a client and this server, the credentials would be exposed.
- 7.5 High severity
Field Analytics: Exposure of Sensitive Information to an Unauthorized Actor
A remote unauthorized attacker may gather sensitive information of the application, due to missing authorization of configuration settings of the product.
- 7.5 High severity
SICK Media Server: Cleartext Transmission of Sensitive Information
All communication with the REST API is unencrypted (HTTP), allowing an attacker to intercept traffic between an actor and the webserver. This leads to the possibility of information gathering and downloading media files.
- 9.8 Critical severity
SICK Media Server: Inclusion of Sensitive Information in Source Code
Files in the source code contain login credentials for the admin user and the property configuration password, allowing an attacker to get full access to the application.
- 8.6 High severity
SICK Media Server: Missing Authorization
Due to missing authorization of an API endpoint, unauthorized users can send HTTP GET requests to gather sensitive information. An attacker could also send HTTP POST requests to modify the log files’ root path as well as the TCP ports the service is running on
- 9.8 Critical severity
SICK DL100-2xxxxxxx: Use of Weak Hash
The device uses a weak hashing alghorithm to create the password hash. Hence, a matching password can be easily calculated by an attacker. This impacts the security and the integrity of the device.
- 7.5 High severity
SICK DL100-2xxxxxxx: Cleartext Transmission of Sensitive Information
The device uses an unencrypted, proprietary protocol for communication. Through this protocol, configuration data is transmitted and device authentication is performed. An attacker can thereby intercept the authentication hash and use it to log into the device
- 9.3 Critical severity
SICK DL100-2xxxxxxx: Download of Code Without Integrity Check
The product can be used to distribute malicious code using SDD Device Drivers due to missing download verification checks, leading to code execution on target systems.
- 8.8 High severity
SICK Lector8xx: Improper Neutralization of Special Elements used in a Command
The vulnerability may allow a remote low priviledged attacker to run arbitrary shell commands by using lower-level functions to interact with the device.
- 8.8 High severity
SICK Lector8xx: Improper Enforcement of Message Integrity During Transmission in a Communication Channel
The vulnerability may allow a remote low priviledged attacker to run arbitrary shell commands by manipulating the firmware file and uploading it to the device.
- 9.9 Critical severity
SICK MEAC300: Insufficiently Protected Credentials
The standard user uses the run as function to start the MEAC applications with administrative privileges. To ensure that the system can startup on its own, the credentials of the administrator were stored. Consequently, the EPC2 user can execute any command wi
- 8.2 High severity
SICK InspectorP61x: Missing Authentication for Critical Functionality
Lua apps can be deployed, removed, started, reloaded or stopped without authorization via AppManager. This allows an attacker to remove legitimate apps creating a DoS attack, read and write files or load apps that use all features of the product available to a
- 7.3 High severity
SICK InspectorP61x: Missing Authentication for Critical Functionality
Unauthenticated CROWN APIs allow access to critical functions. This leads to the accessibility of large parts of the web application without authentication.
- 9.0 Critical severity
SICK InspectorP61x: Hidden Functionality
The product is vulnerable to pass-the-hash attacks in combination with hardcoded credentials of hidden user levels. This means that an attacker can log in with the hidden user levels and gain full access to the device.