CVE-2024-52925
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceOPSWAT MetaDefender Kiosk before version 4.7.0 contains an arbitrary code execution vulnerability in the Unlock Device feature used for software-encrypted USB drives. An attacker with access to the Kiosk's USB unlock functionality can execute arbitrary code by exploiting how the software handles software-encrypted USB devices.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Physical
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed MetaDefender Kiosk versionLocate the version information in the application (typically in Help > About, Settings > System Info, or the main dashboard). If available via command line, check the executable version or look in the installation directory for a version file.Affected if The installed version is lower than 4.7.0 (for example, 4.6.x, 4.5.x, or earlier)
-
Confirm the Unlock Device feature is enabledAccess the Kiosk administrative interface or configuration panel. Navigate to the device unlock or USB management settings. Verify whether the Unlock Device functionality is turned on.Affected if The Unlock Device feature is enabled and accessible to users
-
Check software-encrypted USB support configurationIn the Kiosk settings, locate the USB device handling or encryption settings. Determine if support for software-encrypted USB drives is enabled or configurable.Affected if Software-encrypted USB device support is enabled in the configuration
-
Assess physical access to the USB unlock interfaceDetermine whether untrusted individuals can physically access the Kiosk and reach the USB unlock functionality without authentication barriers.Affected if The USB unlock feature is accessible to unauthenticated or untrusted users
A user is affected if the Kiosk is running a version before 4.7.0 AND the Unlock Device feature for software-encrypted USB drives is enabled and accessible in the environment.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpdate MetaDefender Kiosk to version 4.7.0 or later to obtain the patch for this vulnerability. Restrict physical access to the Kiosk's USB unlock feature until the update can be applied.
MetaDefender Kiosk 4.7.0 or later
- Back up the current MetaDefender Kiosk configuration and any critical data
- Download OPSWAT MetaDefender Kiosk version 4.7.0 or later from the official OPSWAT vendor website or support portal
- Follow the official upgrade documentation to install the new version, ensuring proper service shutdown before upgrade
- After upgrade, verify the MD Kiosk Unlock Device feature is functioning correctly
- Confirm the version number reflects 4.7.0 or later in the product interface
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-52925 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-52925 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data