# CVE-2025-1879: i-Drive i11/i12 APK hard-coded credentials

> Attackers with physical access can extract hard-coded credentials from the i-Drive mobile application, potentially bypassing security controls.

- **Severity:** Low 2.4 (`CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Mar 2025
- **Updated:** 4 Mar 2025
- **Also known as:** GHSA-7qvr-xp68-rqhm

## What is CVE-2025-1879?

CVE-2025-1879 is a low-severity 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.

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

Weakness: CWE-798 (Use of Hard-coded Credentials), CWE-259 (Use of Hard-coded Password)

## Which versions are affected by CVE-2025-1879?

It affects 2 products.


Products: I-Drive I11 Firmware, I-Drive I12 Firmware.

## How do I fix CVE-2025-1879?

No fix has been published for CVE-2025-1879 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-1879 being exploited?

There is no known exploitation of CVE-2025-1879 in the wild and no public exploit code.

## Other vulnerabilities in i-Drive i11

- [CVE-2025-1881](https://insights.sbomify.com/CVE-2025-1881/): i-Drive i11/i12 Video Footage/Live Video Stream access control (medium 5.3)
- [CVE-2025-1878](https://insights.sbomify.com/CVE-2025-1878/): i-Drive i11/i12 WiFi default password (low 2.3)
- [CVE-2025-1882](https://insights.sbomify.com/CVE-2025-1882/): i-Drive i11/i12 Device Setting improper access control for register interface (low 2.3)
- [CVE-2025-1880](https://insights.sbomify.com/CVE-2025-1880/): i-Drive i11/i12 Device Pairing authentication bypass (low 1.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-1879 and fix it if it is affected.

What it is: CVE-2025-1879 is a low-severity 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.
Exploitation: There is no known exploitation of CVE-2025-1879 in the wild and no public exploit code.

Affected product: i-Drive i11. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-1879/ (Markdown: https://insights.sbomify.com/CVE-2025-1879/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-1879
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-1879
- OSV: https://osv.dev/vulnerability/CVE-2025-1879

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-1879/
Summaries are generated and may contain mistakes; the official description above is the record.