SICK AG

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.

SICK Package Analytics software up to and including version V04.0.0 are vulnerable to an authentication bypass by directly interfacing with the REST API.

Multiple endpoints with sensitive information do not require authentication, making the application susceptible to information gathering.

In the HTTP request, the username and password are transferred directly in the URL as parameters.

A remote unauthorized attacker may gather sensitive information of the application, due to missing authorization of configuration settings of the product.

The product does not implement sufficient measures to prevent multiple failed authentication attempts within a short time frame, making it susceptible to brute-force attacks.

SICK Package Analytics software up to and including version V04.0.0 are vulnerable due to incorrect default permissions settings.

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.

It's possible to brute force folders and files, what can be used by an attacker to steal sensitve information.

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.

For failed login attempts, the application returns different error messages depending on whether the login failed due to an incorrect password or a non-existing username.

Due to a lack of authentication, it is possible for an unauthenticated user to request data from this endpoint, making the application vulnerable for user enumeration.

Passwords are stored in plain text within the configuration of SICK Package Analytics software up to and including V04.1.1.

When an error occurs in the application a full stacktrace is provided to the user.

The application fails to implement several security headers.

JavaScript can be ran inside the address bar via the dashboard "Open in new Tab" Button, making the application vulnerable to session hijacking.