{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-28099 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-28099 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-28099 is a high-severity vulnerability in KEYENCE CORPORATION VT STUDIO, published on 15 Apr 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-28099 and fix it if it is affected.\n\nWhat it is: CVE-2024-28099 is a high-severity vulnerability in KEYENCE CORPORATION VT STUDIO, published on 15 Apr 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2024-28099 in the wild and no public exploit code.\n\nAffected product: KEYENCE CORPORATION VT STUDIO. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-28099/ (Markdown: https://insights.sbomify.com/CVE-2024-28099/index.md)","id":"CVE-2024-28099","markdown":"https://insights.sbomify.com/CVE-2024-28099/index.md","name":"CVE-2024-28099","record":{"aliases":["GHSA-h3gg-f2jm-62h3"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"VT STUDIO","requires_auth":"none","summary":"An attacker can execute arbitrary code via DLL search path hijacking in VT STUDIO, requiring user interaction to launch the application.","user_interaction":"required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jpcert","cpe":[{"product":"vt_studio","vendor":"keyence"}],"cvss":{"score":7.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-427","name":"Uncontrolled Search Path Element"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Other in VT STUDIO","id":"CVE-2024-28099","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Stored Cross-site Scripting leading to arbitrary actions taken on behalf of users in elabftw","id":"CVE-2024-28100"},"packages":[],"prev":{"headline":"Apache Pulsar: Improper Authorization For Topic-Level Policy Management","id":"CVE-2024-28098"},"products":["VT STUDIO"],"published":"2024-04-15","related":[{"cvss_score":7.1,"headline":"Memory corruption in VT STUDIO","id":"CVE-2025-58777","kev_date_added":null,"published":"2025-10-02"},{"cvss_score":7.1,"headline":"Memory corruption in VT STUDIO","id":"CVE-2025-61691","kev_date_added":null,"published":"2025-10-02"},{"cvss_score":7.1,"headline":"Use after free in VT STUDIO","id":"CVE-2025-61692","kev_date_added":null,"published":"2025-10-02"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-08-08","vendors":["KEYENCE CORPORATION"]},"summary":"An attacker can execute arbitrary code via DLL search path hijacking in VT STUDIO, requiring user interaction to launch the application.","url":"https://insights.sbomify.com/CVE-2024-28099/"}