{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2025-1880 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-1880 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-1880 is a low-severity authentication bypass vulnerability in i-Drive i11, published on 3 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-1880 and fix it if it is affected.\n\nWhat it is: CVE-2025-1880 is a low-severity authentication bypass vulnerability in i-Drive i11, published on 3 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-1880 in the wild and no public exploit code.\n\nAffected product: i-Drive i11. 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-1880/ (Markdown: https://insights.sbomify.com/CVE-2025-1880/index.md)","id":"CVE-2025-1880","markdown":"https://insights.sbomify.com/CVE-2025-1880/index.md","name":"CVE-2025-1880","record":{"aliases":["GHSA-2v56-g578-78g2"],"analysis":{"component_type":"iot_embedded","fix_type":"end_of_life","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"i-Drive device","requires_auth":"none","summary":"Attackers with physical access can bypass authentication during device pairing on i-Drive i11 and i12 devices.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"i11_firmware","vendor":"i-drive"},{"product":"i12_firmware","vendor":"i-drive"}],"cvss":{"score":1,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:P/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-305","name":"Authentication Bypass by Primary Weakness"},{"id":"CWE-287","name":"Improper Authentication"}],"description":"A vulnerability was found in i-Drive i11 and i12 up to 20250227. It has been classified as problematic. Affected is an unknown function of the component Device Pairing. The manipulation leads to authentication bypass by primary weakness. It is possible to launch the attack on the physical device. The complexity of an attack is rather high. The exploitability is told to be difficult. It was not possible to identify the current maintainer of the product. It must be assumed that the product is end-of-life.","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":"i-Drive i11/i12 Device Pairing authentication bypass","id":"CVE-2025-1880","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"i-Drive i11/i12 Video Footage/Live Video Stream access control","id":"CVE-2025-1881"},"packages":[],"prev":{"headline":"i-Drive i11/i12 APK hard-coded credentials","id":"CVE-2025-1879"},"products":["i11","i12"],"published":"2025-03-03","related":[{"cvss_score":5.3,"headline":"i-Drive i11/i12 Video Footage/Live Video Stream access control","id":"CVE-2025-1881","kev_date_added":null,"published":"2025-03-03"},{"cvss_score":2.4,"headline":"i-Drive i11/i12 APK hard-coded credentials","id":"CVE-2025-1879","kev_date_added":null,"published":"2025-03-03"},{"cvss_score":2.3,"headline":"i-Drive i11/i12 WiFi default password","id":"CVE-2025-1878","kev_date_added":null,"published":"2025-03-03"},{"cvss_score":2.3,"headline":"i-Drive i11/i12 Device Setting improper access control for register interface","id":"CVE-2025-1882","kev_date_added":null,"published":"2025-03-03"}],"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-03-03","vendors":["i-Drive"]},"summary":"Attackers with physical access can bypass authentication during device pairing on i-Drive i11 and i12 devices.","url":"https://insights.sbomify.com/CVE-2025-1880/"}