Clear text traffic is Enabled For App[android:usesCleartextTraffic=true] The app intends to use cleartext network traffic, such as cleartext HTTP, FTP stacks, DownloadManager, and MediaPlayer. The default value for apps that target API level 27 or lower is "true". Apps that target API level 28 or higher default to "false". The key reason for avoiding cleartext traffic is the lack of confidentiality, authenticity, and protections against tampering; a network attacker can eavesdrop on transmitted data and also modify it without being detected.
Medium
Application Data can be Backed up[android:allowBackup=true] This flag allows anyone to backup your application data via adb. It allows users who have enabled USB debugging to copy application data off of the device.
High
Activity (com.lagradost.cloudstream3.ui.player.DownloadedPlayerActivity) is not Protected. [android:exported=true] An Activity is found to be shared with other apps on the device therefore leaving it accessible to any other application on the device.
High
Broadcast Receiver (com.lagradost.cloudstream3.receivers.VideoDownloadRestartReceiver) is not Protected. [android:exported=true] A Broadcast Receiver is found to be shared with other apps on the device therefore leaving it accessible to any other application on the device.
High
Service (androidx.work.impl.background.systemjob.SystemJobService) is Protected by a permission, but the protection level of the permission should be checked.Permission: android.permission.BIND_JOB_SERVICE [android:exported=true] A Service is found to be shared with other apps on the device therefore leaving it accessible to any other application on the device. It is protected by a permission which is not defined in the analysed application. As a result, the protection level of the permission should be checked where it is defined. If it is set to normal or dangerous, a malicious application can request and obtain the permission and interact with the component. If it is set to signature, only applications signed with the same certificate can obtain the permission.
High
Broadcast Receiver (androidx.work.impl.diagnostics.DiagnosticsReceiver) is Protected by a permission, but the protection level of the permission should be checked.Permission: android.permission.DUMP [android:exported=true] A Broadcast Receiver is found to be shared with other apps on the device therefore leaving it accessible to any other application on the device. It is protected by a permission which is not defined in the analysed application. As a result, the protection level of the permission should be checked where it is defined. If it is set to normal or dangerous, a malicious application can request and obtain the permission and interact with the component. If it is set to signature, only applications signed with the same certificate can obtain the permission.
The application invoke platform-provided DRBG functionality for its cryptographic operations. Random Bit Generation Services
FCS_STO_EXT.1.1
The application does not store any credentials to non-volatile memory. Storage of Credentials
FCS_CKM_EXT.1.1
The application generate no asymmetric cryptographic keys. Cryptographic Key Generation Services
FDP_DEC_EXT.1.1
The application has access to ['network connectivity']. Access to Platform Resources
FDP_DEC_EXT.1.2
The application has access to no sensitive information repositories. Access to Platform Resources
FDP_NET_EXT.1.1
The application has user/application initiated network communications. Network Communications
FDP_DAR_EXT.1.1
The application implement functionality to encrypt sensitive data in non-volatile memory. Encryption Of Sensitive Application Data
FMT_MEC_EXT.1.1
The application invoke the mechanisms recommended by the platform vendor for storing and setting configuration options. Supported Configuration Mechanism
FTP_DIT_EXT.1.1
The application does encrypt some transmitted data with HTTPS/TLS/SSH between itself and another trusted IT product. Protection of Data in Transit
FCS_RBG_EXT.2.1 FCS_RBG_EXT.2.2
The application perform all deterministic random bit generation (DRBG) services in accordance with NIST Special Publication 800-90A using Hash_DRBG. The deterministic RBG is seeded by an entropy source that accumulates entropy from a platform-based DRBG and a software-based noise source, with a minimum of 256 bits of entropy at least equal to the greatest security strength (according to NIST SP 800-57) of the keys and hashes that it will generate. Random Bit Generation from Application
FCS_COP.1.1(1)
The application perform encryption/decryption not in accordance with FCS_COP.1.1(1), AES-ECB mode is being used. Cryptographic Operation - Encryption/Decryption
FCS_COP.1.1(2)
The application perform cryptographic hashing services not in accordance with FCS_COP.1.1(2) and uses the cryptographic algorithm RC2/RC4/MD4/MD5. Cryptographic Operation - Hashing
FCS_HTTPS_EXT.1.1
The application implement the HTTPS protocol that complies with RFC 2818. HTTPS Protocol
FCS_HTTPS_EXT.1.2
The application implement HTTPS using TLS. HTTPS Protocol
FCS_HTTPS_EXT.1.3
The application notify the user and not establish the connection or request application authorization to establish the connection if the peer certificate is deemed invalid. HTTPS Protocol
FIA_X509_EXT.1.1
The application invoked platform-provided functionality to validate certificates in accordance with the following rules: ['The certificate path must terminate with a trusted CA certificate']. X.509 Certificate Validation
FIA_X509_EXT.2.1
The application use X.509v3 certificates as defined by RFC 5280 to support authentication for HTTPS , TLS. X.509 Certificate Authentication
FCS_CKM.1.1(2)
The application shall generate symmetric cryptographic keys using a Random Bit Generator as specified in FCS_RBG_EXT.1 and specified cryptographic key sizes 128 bit or 256 bit. Cryptographic Symmetric Key Generation
MD5 is a weak hash known to have hash collisions.
MASVS: MSTG-CRYPTO-4 CWE-327 Use of a Broken or Risky Cryptographic Algorithm M5: Insufficient Cryptography
Files:
org/mozilla/javascript/tools/shell/Main.java
Medium CVSS:7.4
Files may contain hardcoded sensitive information like usernames, passwords, keys etc.
MASVS: MSTG-STORAGE-14 CWE-312 Cleartext Storage of Sensitive Information M9: Reverse Engineering
The App uses an insecure Random Number Generator.
MASVS: MSTG-CRYPTO-6 CWE-330 Use of Insufficiently Random Values M5: Insufficient Cryptography
Files:
org/jsoup/helper/DataUtil.java
High CVSS:7.4
Insecure WebView Implementation. WebView ignores SSL Certificate errors and accept any SSL Certificate. This application is vulnerable to MITM attacks
MASVS: MSTG-NETWORK-3 CWE-295 Improper Certificate Validation M3: Insecure Communication
App can read/write to External Storage. Any App can read data written to External Storage.
MASVS: MSTG-STORAGE-2 CWE-276 Incorrect Default Permissions M2: Insecure Data Storage
App creates temp file. Sensitive information should never be written into a temp file.
MASVS: MSTG-STORAGE-2 CWE-276 Incorrect Default Permissions M2: Insecure Data Storage
This App uses SSL certificate pinning to detect or prevent MITM attacks in secure communication channel.
MASVS: MSTG-NETWORK-4
Files:
com/uwetrottmann/tmdb2/Tmdb.java
High CVSS:7.4
Insecure Implementation of SSL. Trusting all the certificates or accepting self signed certificates is a critical Security Hole. This application is vulnerable to MITM attacks
MASVS: MSTG-NETWORK-3 CWE-295 Improper Certificate Validation M3: Insecure Communication
The App uses the encryption mode CBC with PKCS5/PKCS7 padding. This configuration is vulnerable to padding oracle attacks.
MASVS: MSTG-CRYPTO-3 CWE-649 Reliance on Obfuscation or Encryption of Security-Relevant Inputs without Integrity Checking M5: Insufficient Cryptography