# CVE-2025-22450: Security feature bypass in UD-LT2

> A remote attacker can disable the LAN-side firewall and open specific ports on I-O DATA UD-LT2 devices due to undocumented features.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Jan 2025
- **Updated:** 12 Feb 2025
- **Also known as:** GHSA-6grv-w576-crgf

## What is CVE-2025-22450?

CVE-2025-22450 is a high-severity vulnerability in I-O DATA DEVICE, INC. UD-LT2, published on 22 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Inclusion of undocumented features issue exists in UD-LT2 firmware Ver.1.00.008_SE and earlier. A remote attacker may disable the LAN-side firewall function of the affected products, and open specific ports.

Weakness: CWE-1242 (Inclusion of Undocumented Features or Chicken Bits)

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


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

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

## Is CVE-2025-22450 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-22450 is a high-severity vulnerability in I-O DATA DEVICE, INC. UD-LT2, published on 22 Jan 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-22450 in the wild and no public exploit code.

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

## Sources

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

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