dbcve.org
Uncontrolled Search Path (DLL Hijack)Weakness · CWE-427

CVE-2024-9852

HIGH · 7.8 CVSS v3.1 Published 2024-11-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

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
Uncontrolled Search Path Element vulnerability in Mitsubishi Electric GENESIS64 versions 10.97.3 and prior, Mitsubishi Electric ICONICS Suite versions 10.97.3 and prior, Mitsubishi Electric Hyper Historian versions 10.97.3 and prior, Mitsubishi Electric GENESIS32 all versions, Mitsubishi Electric MC Works64 all versions, Mitsubishi Electric Iconics Digital Solutions GENESIS64 versions 10.97.3 and prior, Mitsubishi Electric Iconics Digital Solutions ICONICS Suite versions 10.97.3 and prior, Mitsubishi Electric Iconics Digital Solutions Hyper Historian versions 10.97.3 and prior, and Mitsubishi Electric Iconics Digital Solutions GENESIS32 all versions allows a local authenticated attacker to execute a malicious code by storing a specially crafted DLL in a specific folder. This could lead to disclose, tamper with, destroy, or delete information in the affected products, or cause a denial of service (DoS) condition on the products.

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

This is a DLL hijacking vulnerability (uncontrolled search path element) in multiple Mitsubishi Electric and ICONICS industrial software products. A local authenticated attacker can place a malicious DLL in a specific folder that the affected application searches during DLL loading, allowing arbitrary code execution with the application's privileges. This could lead to information disclosure, tampering, destruction, or DoS.

MitigationImplement DLL search order hardening by specifying full paths for all DLL loads, remove unnecessary writable folders from the search path, and restrict folder permissions to prevent unauthorized DLL placement. Coordinate with vendor for official patches.

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

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

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

  1. Identify installed Mitsubishi Electric or ICONICS software
    Review installed programs on the system, check Program Files directories, or use system inventory tools to list industrial automation or SCADA software from these vendors
    Affected if Any Mitsubishi Electric or ICONICS industrial software is installed and the software has not been patched for DLL hijacking
  2. Inspect application folder permissions
    Right-click on the application's installation folder, go to Properties > Security, and check which users or groups have Write or Modify permissions
    Affected if Users other than administrators or the SYSTEM account have Write or Modify permissions to the application directory, allowing them to place malicious DLLs
  3. Review the application's DLL search path
    Use Process Monitor or similar tools to observe DLL search paths when the application starts or loads modules. Look for locations where the application searches for DLLs without full path specification
    Affected if The application searches for DLLs in directories writable by low-privilege users (such as the application directory or subdirectories)
  4. Check for vulnerable folder locations
    Identify folders in the application's DLL search path that are writable by authenticated users, particularly the application base directory, System32, or user-writable subdirectories
    Affected if The application loads DLLs from folders that can be written to by non-admin users, creating the hijacking opportunity
  5. Verify vendor security advisories
    Search Mitsubishi Electric and ICONICS security advisories for CVE-2024-9852 to confirm if your specific product version is listed as affected
    Affected if Your specific product version matches an affected version listed in vendor advisories for this CVE

A user is likely affected if they have installed Mitsubishi Electric or ICONICS industrial software and the application folder or its subdirectories are writable by non-administrative users, allowing 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement DLL search order hardening by specifying full paths for all DLL loads, remove unnecessary writable folders from the search path, and restrict folder permissions to prevent unauthorized DLL placement. Coordinate with vendor for official patches.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-9852 — 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-9852 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