CVE-2025-63433
MediumCVSS 4.6Exploitation Probability (EPSS)
Low risk11th percentile - higher than 11% of all known CVEs
Summary
Xtooltech Xtool AnyScan Android Application 4.40.40 and prior uses a hardcoded cryptographic key and IV to decrypt update metadata. The key is stored as a static value within the application's code. An attacker able to intercept network traffic can use this hardcoded key to decrypt, modify, and re-encrypt the update manifest, directing the application to download a malicious update package.
Risk Assessment
An attacker on the same network can cause installation of a malicious update, potentially leading to device compromise or arbitrary code execution. The risk affects all users of the application on untrusted networks.
Recommendation
Update the application to a version that removes the hardcoded key, or suspend its use until a fix is released. Consider using a VPN or trusted networks during updates.
Other vulnerabilities in Xtool AnyScan
See all- CVE-2025-63434High
The update mechanism in Xtooltech Xtool AnyScan Android Application 4.40.40 and prior is insecure. The application downloads and extracts update packages containing executable code without performing a cryptographic integrity or authenticity check on their contents. An attacker who can control the update metadata can serve a malicious package, which the application will accept, extract, and later execute, leading to arbitrary code execution.
- CVE-2025-63432Medium
Xtooltech Xtool AnyScan Android Application 4.40.40 and prior is missing SSL certificate validation. The application fails to properly validate the TLS certificate from its update server. An attacker on the same network can perform a man-in-the-middle attack to intercept, decrypt, and modify traffic between the application and the update server, serving as the basis for further attacks including remote code execution.
Original NVD description (English source)
Xtooltech Xtool AnyScan Android Application 4.40.40 and prior uses a hardcoded cryptographic key and IV to decrypt update metadata. The key is stored as a static value within the application's code. An attacker with the ability to intercept network traffic can use this hardcoded key to decrypt, modify, and re-encrypt the update manifest, allowing them to direct the application to download a malicious update package.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS