Poor quality of randomness in authorization tokens
The Media Server’s authorization tokens have a poor quality of randomness.
10 records
The Media Server’s authorization tokens have a poor quality of randomness.
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.
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.
The server supports authentication methods in which credentials are sent in plaintext over unencrypted channels.
The application fails to implement several security headers.
The web application is vulnerable to clickjacking attacks.
The HttpOnlyflag of the session cookie \"@@\" is set to false.
All communication with the REST API is unencrypted (HTTP), allowing an attacker to intercept traffic between an actor and the webserver.
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.
Due to missing authorization of an API endpoint, unauthorized users can send HTTP GET requests to gather sensitive information.