Baggage Analytics vulnerabilities
5 known vulnerabilities in Baggage Analytics from SICK. 5 are rated high or critical. Each entry lists the affected versions and the release that fixes it, where the vendor has published one.
Latest first
- 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
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.