i-Drive i11/i12 Device Pairing authentication bypass

published 2025-03-03 last yr. modified 2026-06-17 4mo ago also EUVD-2025-5514

cvss: 2.0; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.3%; EPSS 0.3% chance of exploitation in 30 days, percentile 17%
public exploits: 0; none known

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.

Is CVE-2025-1880 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: partial
Assessed: last yr. (2025-03-03)

Exploit prediction

0.25% chance of exploitation in the next 30 days, higher than 17% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by	version	score	vector
CNA	4.0	1.0	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
CNA	3.1	2.0	CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
CNA	3.0	2.0	CVSS:3.0/AV:P/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
CNA	2.0	1.2	AV:L/AC:H/Au:N/C:P/I:N/A:N
CNA	4.0	1.0	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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD	3.1	4.3	CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Affected products

i-Drive i11
i-Drive i12

Classification

Weakness

CWE-305 Authentication Bypass by Primary Weakness
CWE-287 Improper Authentication

References

vuldb.com /?submit.510951
third-party-advisory, vendor-advisory
vuldb.com /?id.298194
vdb-entry, permissions-required
vuldb.com /?ctiid.298194
signature, permissions-required
github.com /geo-chen/i-Drive
related, third-party-advisory

Sources

CVE List CVE-2025-1880
NVD CVE-2025-1880

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.