{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2025-11633 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-11633 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-11633 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-11633 and fix it if it is affected.\n\nWhat it is: CVE-2025-11633 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: There is no known exploitation of CVE-2025-11633 in the wild and no public exploit code.\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-11633/ (Markdown: https://insights.sbomify.com/CVE-2025-11633/index.md)","id":"CVE-2025-11633","markdown":"https://insights.sbomify.com/CVE-2025-11633/index.md","name":"CVE-2025-11633","record":{"aliases":["GHSA-6rrj-c3mx-rv2m"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Smart pet camera","requires_auth":"none","summary":"Attackers can bypass certificate validation in the log upload script, potentially intercepting or modifying data, affecting Furbo 360 and Mini users.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"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-295","name":"Improper Certificate Validation"},{"id":"CWE-287","name":"Improper Authentication"}],"description":"A vulnerability was identified in Tomofun Furbo 360 and Furbo Mini. Affected by this issue is the function upload_file_to_s3 of the file collect_logs.sh of the component HTTP Traffic Handler. The manipulation leads to improper certificate validation. The attack may be initiated remotely. The attack is considered to have high complexity. The exploitation is known 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":"none_known"},"has_fix":null,"headline":"Tomofun Furbo 360/Furbo Mini HTTP Traffic collect_logs.sh upload_file_to_s3 certificate validation","id":"CVE-2025-11633","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"Tomofun Furbo 360/Furbo Mini UART information disclosure","id":"CVE-2025-11634"},"packages":[],"prev":{"headline":"Call Now Button \u003c= 1.5.4 - Authenticated (Subscriber+) Missing Authorization to Multiple Functions","id":"CVE-2025-11632"},"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 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 MQTT Client Certificate furbo_img hard-coded credentials","id":"CVE-2025-11643","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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-10-16","vendors":["Tomofun"]},"summary":"Attackers can bypass certificate validation in the log upload script, potentially intercepting or modifying data, affecting Furbo 360 and Mini users.","url":"https://insights.sbomify.com/CVE-2025-11633/"}