{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-63432 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-63432 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-63432 is a medium-severity vulnerability in n/a, published on 24 Nov 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-63432 and fix it if it is affected.\n\nWhat it is: CVE-2025-63432 is a medium-severity vulnerability in n/a, published on 24 Nov 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-63432 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-63432/ (Markdown: https://insights.sbomify.com/CVE-2025-63432/index.md)","id":"CVE-2025-63432","markdown":"https://insights.sbomify.com/CVE-2025-63432/index.md","name":"CVE-2025-63432","record":{"aliases":["GHSA-qcqv-64cg-9qm4"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["code_execution","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Android diagnostic app","requires_auth":"low_privilege","summary":"Attackers can perform MITM attacks to intercept and modify update traffic, potentially leading to remote code execution due to missing SSL certificate validation.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"xtool_anyscan","vendor":"xtooltech"}],"cvss":{"score":4.6,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-599","name":"Missing Validation of OpenSSL Certificate"}],"description":"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 (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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Security feature bypass in n/a","id":"CVE-2025-63432","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Hardcoded credentials in n/a","id":"CVE-2025-63433"},"packages":[],"prev":{"headline":"Hardcoded credentials in n/a","id":"CVE-2025-63423"},"products":["n/a"],"published":"2025-11-24","related":[{"cvss_score":8.8,"headline":"Code injection in n/a","id":"CVE-2025-63434","kev_date_added":null,"published":"2025-11-24"},{"cvss_score":4.6,"headline":"Hardcoded credentials in n/a","id":"CVE-2025-63433","kev_date_added":null,"published":"2025-11-24"},{"cvss_score":4.3,"headline":"Missing authorization in n/a","id":"CVE-2025-63435","kev_date_added":null,"published":"2025-11-24"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-11-24","vendors":["n/a"]},"summary":"Attackers can perform MITM attacks to intercept and modify update traffic, potentially leading to remote code execution due to missing SSL certificate validation.","url":"https://insights.sbomify.com/CVE-2025-63432/"}