# CVE-2025-32002: Command injection in HDL-T1NV

> Remote unauthenticated attackers can execute arbitrary OS commands on I-O DATA NAS devices if the Remote Link3 function is enabled.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 May 2025
- **Updated:** 15 May 2025
- **Also known as:** GHSA-8x6j-j8rc-9m7p

## What is CVE-2025-32002?

CVE-2025-32002 is a critical command injection vulnerability in I-O DATA DEVICE, INC. HDL-T1NV, published on 15 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Improper neutralization of special elements used in an OS command ('OS Command Injection') issue exists in I-O DATA network attached hard disk 'HDL-T Series' firmware Ver.1.21 and earlier when 'Remote Link3 function' is enabled. If exploited, a remote unauthenticated attacker may execute an arbitrary OS command.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


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

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

## Is CVE-2025-32002 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-32002 is a critical command injection vulnerability in I-O DATA DEVICE, INC. HDL-T1NV, published on 15 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-32002 in the wild and no public exploit code.

Affected product: I-O DATA DEVICE, INC. HDL-T1NV. 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-32002/ (Markdown: https://insights.sbomify.com/CVE-2025-32002/index.md)
```

## Sources

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

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