# CVE-2025-1425: File Read Through Improper Sudo Privilege Management

> Attackers can read arbitrary files on PocketBook InkPad Color 3 devices due to improper sudo privilege management, leading to data exposure.

- **Severity:** Medium 4.7 (`CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:H/SI:H/SA:H`)
- **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:** 4 Mar 2025
- **Updated:** 4 Mar 2025
- **Also known as:** GHSA-wm67-cvpp-xg5f

## What is CVE-2025-1425?

CVE-2025-1425 is a medium-severity vulnerability in PocketBook InkPad Color 3, published on 4 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A Sudo privilege misconfiguration vulnerability in PocketBook InkPad Color 3 on Linux, ARM allows attackers to read file contents on the device.This issue affects InkPad Color 3: U743k3.6.8.3671.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2025-1425 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-1425 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-1425 is a medium-severity vulnerability in PocketBook InkPad Color 3, published on 4 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-1425 exists.

Affected product: PocketBook InkPad Color 3. 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-1425/ (Markdown: https://insights.sbomify.com/CVE-2025-1425/index.md)
```

## Sources

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

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