Menu

Star on GitHub · 3.2k

CVE-2025-1879

2.4 · LOW

A vulnerability was found in i-Drive i11 and i12 up to 20250227 and classified as problematic.

Published Mar 3, 2025CWE-259EPSS 0.24%

Overview

CVE-2025-1879 is a low-severity vulnerability. It was published on March 3, 2025 and has a CVSS 3.1 base score of 2.4 (LOW).

This vulnerability has a CVSS 3.1 base score of 2.4, rated LOW. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

Technical description

A vulnerability was found in i-Drive i11 and i12 up to 20250227 and classified as problematic. This issue affects some unknown processing of the component APK. The manipulation leads to hard-coded credentials. It is possible to launch the attack on the physical device. It was not possible to identify the current maintainer of the product. It must be assumed that the product is end-of-life.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2025-1879?

CVE-2025-1879 is a low-severity vulnerability. It was published on March 3, 2025 and has a CVSS 3.1 base score of 2.4 (LOW).

How severe is CVE-2025-1879?

This vulnerability has a CVSS 3.1 base score of 2.4, rated LOW. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2025-1879?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2025-1879?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2025-1879 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related LOW CVEs from 2025

View all