Skip to content
OpenAdvisories

Product · SICK

SICK Media Server

9 known vulnerabilities.

SICK Media Server at a glance

Last 12 months
0
Critical · all time
0
Exploited · all time
0
Public exploit · all time
0
New vulnerabilities per month · last 12 months
0 1 1 December 2025: 0 vulnerabilities Dec 2025 January 2026: 0 vulnerabilities February 2026: 0 vulnerabilities March 2026: 0 vulnerabilities Mar April 2026: 0 vulnerabilities May 2026: 0 vulnerabilities June 2026: 0 vulnerabilities Jun July 2026: 0 vulnerabilities August 2026: 0 vulnerabilities September 2026: 0 vulnerabilities Sep October 2026: 0 vulnerabilities November 2026: 0 vulnerabilities
Show as table
MonthVulnerabilitiesCritical
Nov 202600
Oct 202600
Sep 202600
Aug 202600
Jul 202600
Jun 202600
May 202600
Apr 202600
Mar 202600
Feb 202600
Jan 202600
Dec 202500
Nov 202500
Oct 202500
Sep 202500
Aug 202500
Jul 202500
Jun 202590
May 202500
Apr 202500
Mar 202500
Feb 202500
Jan 202500
Dec 202400

9 results · Feed

  • Low 3.1

    Poor quality of randomness in authorization tokens

    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.

  • Medium 6.5

    Deprecated TLS version supported

    The application uses a weak password hash function, allowing an attacker to crack the weak password hash to gain access to an FTP user account.

  • Medium 5.3

    No protection against brute-force attacks

    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.

  • High 7.5

    Unencrypted communication

    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.

  • Medium 4.3

    Clickjacking

    The web application is vulnerable to clickjacking attacks. The site can be embedded into another frame, allowing an attacker to trick a user into clicking on something different from what the user perceives. This could potentially reveal confidential informat…

  • Medium 5.3

    Cookie missing HttpOnly flag

    The HttpOnlyflag of the session cookie \"@@\" is set to false. Since this flag helps preventing access to cookies via client-side scripts, setting the flag to false can lead to a higher possibility of Cross-Side-Scripting attacks which target the stored cooki…

  • High 7.5

    Unencrypted communication (HTTP)

    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.

  • High 7.5

    Credential disclosure

    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.

  • High 8.6

    Configurations endpoint does not require 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 o…