{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-63433 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-63433 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-63433 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-63433 and fix it if it is affected.\n\nWhat it is: CVE-2025-63433 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-63433 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-63433/ (Markdown: https://insights.sbomify.com/CVE-2025-63433/index.md)","id":"CVE-2025-63433","markdown":"https://insights.sbomify.com/CVE-2025-63433/index.md","name":"CVE-2025-63433","record":{"aliases":["GHSA-j9pq-93r5-c843"],"analysis":{"component_type":"mobile_application","fix_type":"no_fix_stated","impacts":["code_execution","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Android diagnostic app","requires_auth":"low_privilege","summary":"Attackers can intercept network traffic to decrypt and modify update metadata using a hardcoded key, forcing the app to install malicious updates.","user_interaction":"required","vuln_class":"hardcoded_credentials"},"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-798","name":"Use of Hard-coded Credentials"}],"description":"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.","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":"Hardcoded credentials in n/a","id":"CVE-2025-63433","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Code injection in n/a","id":"CVE-2025-63434"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2025-63432"},"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":"Security feature bypass in n/a","id":"CVE-2025-63432","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 intercept network traffic to decrypt and modify update metadata using a hardcoded key, forcing the app to install malicious updates.","url":"https://insights.sbomify.com/CVE-2025-63433/"}