i-Drive i11/i12 up to 20250227 Device Pairing authentication bypass

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
2.0$0-$5k0.00

Summaryinfo

A vulnerability categorized as problematic has been discovered in i-Drive i11 and i12 up to 20250227. The affected element is an unknown function of the component Device Pairing. The manipulation results in authentication bypass. This vulnerability is cataloged as CVE-2025-1880. An attack on the physical device is feasible. There is no exploit available. It was not possible to identify the current maintainer of the product. It must be assumed that the product is end-of-life.

Detailsinfo

A vulnerability was found in i-Drive i11 and i12 up to 20250227. It has been classified as problematic. Affected is an unknown functionality of the component Device Pairing. The manipulation with an unknown input leads to a authentication bypass vulnerability. CWE is classifying the issue as CWE-305. The authentication algorithm is sound, but the implemented mechanism can be bypassed as the result of a separate weakness that is primary to the authentication error. This is going to have an impact on confidentiality.

The advisory is available at github.com. This vulnerability is traded as CVE-2025-1880. The exploitability is told to be difficult. Local access is required to approach this attack. The exploitation doesn't require any form of authentication. The technical details are unknown and an exploit is not available.

It was not possible to identify the current maintainer of the product. It must be assumed that the product is end-of-life.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Vendor

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 2.0
VulDB Meta Temp Score: 2.0

VulDB Base Score: 2.0
VulDB Temp Score: 2.0
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Authentication bypass
CWE: CWE-305 / CWE-287
CAPEC: 🔍
ATT&CK: 🔍

Physical: Yes
Local: Yes
Remote: No

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

03/03/2025 🔍
03/03/2025 +0 days 🔍
03/03/2025 +0 days 🔍

Sourcesinfo

Advisory: github.com
Status: Not defined

CVE: CVE-2025-1880 (🔍)
GCVE (CVE): GCVE-0-2025-1880
GCVE (VulDB): GCVE-100-298194

Entryinfo

Created: 03/03/2025 13:30
Changes: 03/03/2025 13:30 (52)
Complete: 🔍
Submitter: geochen
Cache ID: 216::103

Submitinfo

Accepted

  • Submit #510951: i-DRIVE Dashcam i11, i12 Authentication Bypass by Primary Weakness (by geochen)

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Interested in the pricing of exploits?

See the underground prices here!