# CVE-2024-52925: Code injection in MetaDefender Kiosk

> Attackers can execute arbitrary code via the Unlock Device feature for encrypted USB drives in OPSWAT MetaDefender Kiosk.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A: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:** 26 Feb 2025
- **Updated:** 26 Feb 2025

## What is CVE-2024-52925?

CVE-2024-52925 is a medium-severity code injection vulnerability in OPSWAT MetaDefender Kiosk, published on 26 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In OPSWAT MetaDefender Kiosk before 4.7.0, arbitrary code execution can be performed by an attacker via the MD Kiosk Unlock Device feature for software encrypted USB drives.

Weakness: CWE-94 (Improper Control of Generation of Code)

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


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

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

## Is CVE-2024-52925 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-52925 is a medium-severity code injection vulnerability in OPSWAT MetaDefender Kiosk, published on 26 Feb 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-2024-52925 in the wild and no public exploit code.

Affected product: OPSWAT MetaDefender Kiosk. 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-52925/ (Markdown: https://insights.sbomify.com/CVE-2024-52925/index.md)
```

## Sources

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

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