# CVE-2024-52564: Security feature bypass in UD-LT1

> Remote attackers can disable the firewall via undocumented features, enabling arbitrary OS command execution and configuration changes on I-O DATA routers.

- **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:** 5 Dec 2024
- **Updated:** 29 Jan 2025
- **Also known as:** GHSA-4x5w-w3cm-m967

## What is CVE-2024-52564?

CVE-2024-52564 is a high-severity vulnerability in I-O DATA DEVICE, INC. UD-LT1, published on 5 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Inclusion of undocumented features or chicken bits issue exists in UD-LT1 firmware Ver.2.1.8 and earlier and UD-LT1/EX firmware Ver.2.1.8 and earlier. A remote attacker may disable the firewall function of the affected products. As a result, an arbitrary OS command may be executed and/or configuration settings of the device may be altered.

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

## Which versions are affected by CVE-2024-52564?


## How do I fix CVE-2024-52564?

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

## Is CVE-2024-52564 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-52564 and fix it if it is affected.

What it is: CVE-2024-52564 is a high-severity vulnerability in I-O DATA DEVICE, INC. UD-LT1, published on 5 Dec 2024. 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-2024-52564 in the wild and no public exploit code.

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

## Sources

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

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