dbcve.org
Vt StudioApplication · Keyence

CVE-2024-28099

HIGH · 7.8 CVSS v3.1 Published 2024-04-15
Fix available
A fix is available. Upgrade to after 8.32 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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 · unedited
VT STUDIO Ver.8.32 and earlier contains an issue with the DLL search path, which may lead to insecurely loading Dynamic Link Libraries. As a result, arbitrary code may be executed with the privileges of the running application.

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 · high confidence

VT STUDIO versions 8.32 and earlier contains an insecure DLL search path vulnerability where the application loads dynamic link libraries from locations that can be controlled by attackers. This allows a malicious DLL to be loaded in place of a legitimate one, resulting in arbitrary code execution with the privileges of the running application.

MitigationUpgrade VT STUDIO to a version newer than 8.32 if available. If no update exists, implement secure DLL loading by specifying full paths to DLLs, removing insecure paths from the search order, and/or using Windows API functions like SetDllDirectory to constrain DLL loading paths.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Vt StudioApplication
Affected:<= 8.32

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify VT STUDIO version
    Open VT STUDIO and navigate to Help > About, or check the program file properties (right-click the executable > Properties > Details) to find the version number
    Affected if The version is 8.32 or any version lower than 8.32
  2. Locate VT STUDIO installation directory
    Find the installation folder, typically in C:\Program Files\KEYENCE\VT Studio or C:\Program Files (x86)\KEYENCE\VT Studio
    Affected if The application is installed and accessible to untrusted users who could place malicious DLLs in the application directory or search paths
  3. Check for insecure DLL search paths
    Use Process Monitor or examine the application startup with dependency walker to observe which DLL locations are being searched during load. Look for loading from the application directory, current working directory, or system paths without full path specification
    Affected if The application loads DLLs without using full qualified paths or without calling SetDllDirectory to restrict search paths, allowing DLL planting attacks
  4. Verify application privileges
    Check the account context VT STUDIO runs under by opening Task Manager, finding the VT STUDIO process, and viewing the user name
    Affected if VT STUDIO runs with elevated privileges or with access to sensitive resources, making DLL hijacking more impactful
  5. Assess user filesystem access
    Determine if non-admin users can write to directories in the DLL search order for VT STUDIO, including the application directory, system temp folders, or directories added to PATH
    Affected if Untrusted users can write to any directory that VT STUDIO searches for DLLs before system directories

You are affected if VT STUDIO version is 8.32 or earlier AND the application loads DLLs from directories writable by untrusted users, allowing potential DLL hijacking.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 8.32
Interim mitigation

Upgrade VT STUDIO to a version newer than 8.32 if available. If no update exists, implement secure DLL loading by specifying full paths to DLLs, removing insecure paths from the search order, and/or using Windows API functions like SetDllDirectory to constrain DLL loading paths.

Recommended fix Moderate confidence

VT Studio version higher than 8.32 (contact Keyence for exact fixed release)

  1. Check the current installed version of VT Studio by opening the application or checking the About section
  2. Visit the official Keyence website (www.keyence.com) or contact Keyence technical support to obtain the latest version of VT Studio
  3. Download and install the latest version of VT Studio (version higher than 8.32) which contains the fix for the DLL search path vulnerability
  4. After upgrading, verify the application runs correctly and confirm the version number has been updated

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Vt Studio Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-28099 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-28099 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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