{"answers":{"affected":"It affects 2 products.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-11643 exists.","fix":"No fix has been published for CVE-2025-11643 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-11643 is a medium-severity vulnerability in Tomofun Furbo 360, published on 12 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-11643 and fix it if it is affected.\n\nWhat it is: CVE-2025-11643 is a medium-severity vulnerability in Tomofun Furbo 360, published on 12 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-11643 exists.\n\nAffected product: Tomofun Furbo 360. 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-11643/ (Markdown: https://insights.sbomify.com/CVE-2025-11643/index.md)","id":"CVE-2025-11643","markdown":"https://insights.sbomify.com/CVE-2025-11643/index.md","name":"CVE-2025-11643","record":{"aliases":["GHSA-jw33-cfxv-r7r3"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Smart pet camera","requires_auth":"none","summary":"Hardcoded credentials in the MQTT client certificate allow remote attackers to bypass security controls and access device data.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"furbo_360_dog_camera_firmware","vendor":"furbo"},{"product":"furbo_mini_firmware","vendor":"furbo"}],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X","version":"4.0"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"},{"id":"CWE-259","name":"Use of Hard-coded Password"}],"description":"A security flaw has been discovered in Tomofun Furbo 360 and Furbo Mini. Affected by this vulnerability is an unknown functionality of the file /squashfs-root/furbo_img of the component MQTT Client Certificate. Performing manipulation results in hard-coded credentials. The attack may be initiated remotely. The attack's complexity is rated as high. The exploitation appears to be difficult. The firmware versions determined to be affected are Furbo 360 up to FB0035_FW_036 and Furbo Mini up to MC0020_FW_074. The vendor was contacted early about this disclosure but did not respond in any way.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Tomofun Furbo 360/Furbo Mini MQTT Client Certificate furbo_img hard-coded credentials","id":"CVE-2025-11643","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"Tomofun Furbo 360/Furbo Mini UART sensitive information","id":"CVE-2025-11644"},"packages":[],"prev":{"headline":"Tomofun Furbo 360/Furbo Mini Registration denial of service","id":"CVE-2025-11642"},"products":["Furbo 360","Furbo Mini"],"published":"2025-10-12","related":[{"cvss_score":7.3,"headline":"Tomofun Furbo 360/Furbo Mini Root Account hard-coded password","id":"CVE-2025-11649","kev_date_added":null,"published":"2025-10-12"},{"cvss_score":6.3,"headline":"Tomofun Furbo 360/Furbo Mini HTTP Traffic collect_logs.sh upload_file_to_s3 certificate validation","id":"CVE-2025-11633","kev_date_added":null,"published":"2025-10-12"},{"cvss_score":6.3,"headline":"Tomofun Furbo 360 Account server-side request forgery","id":"CVE-2025-11636","kev_date_added":null,"published":"2025-10-12"},{"cvss_score":6.3,"headline":"Tomofun Furbo 360/Furbo Mini GATT Interface URL TF_FQDN.json server-side request forgery","id":"CVE-2025-11648","kev_date_added":null,"published":"2025-10-12"},{"cvss_score":5.3,"headline":"Tomofun Furbo 360 File Upload resource consumption","id":"CVE-2025-11635","kev_date_added":null,"published":"2025-10-12"},{"cvss_score":5.3,"headline":"Tomofun Furbo 360 Audio race condition","id":"CVE-2025-11637","kev_date_added":null,"published":"2025-10-12"}],"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-10-18","vendors":["Tomofun"]},"summary":"Hardcoded credentials in the MQTT client certificate allow remote attackers to bypass security controls and access device data.","url":"https://insights.sbomify.com/CVE-2025-11643/"}