CVE-2025-63432
Xtooltech Xtool Anyscan ≤ 4.40.40
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:NSummary
CVE-2025-63432 is a medium-severity Missing Validation of OpenSSL Certificate (CWE-599) vulnerability in Xtooltech Xtool Anyscan. Its CVSS base score is 4.6 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Adversary-in-the-Middle (T1557); ranked at the 6th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to IA-5 (Authenticator Management) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-198967
Vulnerability Data
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 exploit this vulnerability by performing a Man-in-the-Middle…
more
(MITM) attack to intercept, decrypt, and modify traffic between the application and the update server. This serves as the basis for further attacks, including Remote Code Execution.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V12.3.5V17.2.8
Mitigating Controls (NIST 800-53 r5) AI
Authenticator management requires verification of certificate identity and revocation status before use, directly stopping acceptance of unvalidated OpenSSL certificates.
Security engineering principles require correct implementation of cryptographic authentication mechanisms including certificate validation.
Requiring cryptographic integrity protection for transmitted data forces proper certificate validation to establish trusted channels.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Proper data-in-transit protection via TLS requires certificate validation with SSL_get_verify_result().
Secure development practices include implementing correct OpenSSL certificate validation during coding.
Service and hardware authentication depends on valid certificates, but the control is broader than TLS validation.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing could detect missing certificate validation but does not prevent the weakness at development time.
Mandates proper use of cryptography including certificate validation, directly addressing the missing SSL_get_verify_result() check.
Application security requirements may specify certificate validation but do not mandate the specific OpenSSL API usage.
Requires secure coding practices that would include proper certificate validation in OpenSSL usage.